The next release in 5.0.x series

5.0.1, the first bugfix release in the 5.0.x series, seems to be around the next corner, see Now it would be a good time to test the nightlies, see

At the moment it’s uncertain whether there will be 5.0.2 because 5.1 is relatively near. Maybe it will be decided after 5.0.1. I’ll try to keep you informed.


There were still some problems with OS X build. See and also Trouble after installing Kicad 5.0 on my Mac (running macOS Mojave). Unless new critical bugs are found it looks like 5.0.1 is very near. Well, everything is relative, so I don’t tell what I mean by “very near”…

And more general bugs are still being squished

Wayne’s “last call”:

1 Like

Wayne said he tagged 5.0.1 in the source code. See the mail thread linked in the previous post.

The library is also already tagged. We checked which changes exist in the symbol lib that would break designs. The results are documented here:

We will keep the lib stable till after 5.1 (At that stage we will open it up for v6 development. If we have enough resources then we might have a separate v5 branch for bugfixes.)

1 Like

Will a 5.0.1rc be available or will it be the “final” version ?

It’s a bugfix release so there was no need for an RC. There were separate nightly builds, however.

1 Like

There will be a 5.0.1-rc1 kind of thing for windows at least. I will try to remember to update in this thread.

1 Like

Will a 5 0 1 project open in 5.0.0?
I don’t think that there are any format changes

5.0.1 is a bugfix only release (as far as i am aware)
There should not be incompatibilities to 5.0.0 (If there are then it is probably a bug)


File formats will remain unchanged for the entire 5.x cycle. This will include 5.1


Will the 5.0.1 release have MacOS Action scripts re-enabled? Action scripts were working on nightlies prior to the release of 5.0.0 but action scripting was switched off for the current 5.0.0 release - not sure why. The scripting console works fine.

OK, that means that we can advise users that it should be safe to upgrade 5.0.0 to 5.0.1 when it is released.

Thanks for the next great release of KiCad!

Two questions, from a packagers point of view:

  1. Is there already a changelog available, listing user visible changes.

  2. As 5.0.1 is just a bugfix release, it should be safe to use it with the libraries from 5.0.0, correct? Especially the 3d packages are a huge download (not everyone has an uncapped and fast internet connection), so not forcing (just recommending) an update would be welcome.

That is something you need to ask the devs over at the mailing list.


Thats what delta packages are there for. dfn (fedora, redhat, …) supports it for years now and i would guess apt (debian, ubuntu, mint, …) should also support it. (Windows and maybe also mac are a different story)

Another option is to use git itself. This requires the libs to be separate packages such that the user can select not to install them via the normal packages. (Sadly again maybe not done this way for all platforms. Windows for example does not offer such a package)

You can just go to GitHub and manually select recently changed models of interest.
It is a pity that there is no rsync option.

I’m pretty sure that If you clone the git repo, and do a pull, you will get the diff and not download the whole thing again.

1 Like

Thanks, will do.

So does openSUSE (these are the guys who invented it …), but only for regular releases. For TW and addon repos, it is to much churn.

Although for the kicad-packages3D rpm, it is not really a big gain - after 12 minutes of processing (i7-4790), you end up with a 200 MByte drpm instead of the regular 320 MByte rpm.

This would be an option if it were better integrated in the library manager - i.e. already added with a download/refresh button. Or just a “Download packages for all footprints used in the current layout.” button.

Would it be easier if there is a dialog inside kicad? Yes it would.
But saying this is not an option without it is simply wrong on so many levels.

You really do not need to include everything into the same toolset. Git at this level is really not hard to understand. (This sort of thing is easily doable within any git gui)

1 Like