What configuration tool are you referring to?
RC3 tagged!
https://lists.launchpad.net/kicad-developers/msg36380.html
Does anyone know if the 01JUL18 nightly is the RC3?
Yes, the build r10601 is the first (and only, for now) rc3.
2 Likes
R10601 (RC3) binaries for Windows can be found here (in case somebody doesn’t know):
http://downloads.kicad.org/windows/nightly/
In the dev mailing list Wayne told that 20th this month is the target date for tagging 5.0.0. But it depends on the bug situation. https://lists.launchpad.net/kicad-developers/msg36455.html
Edit: the “release date” could be 27th.
1 Like
If you are using a stable V4 release, and do not have a mission critical project in the works, then I suggest you grab a recent nightly of V5RC3. You will probably have a better transition experience if you read up a little bit on the forum about Environment Variables; this is not clearly going to be “fixed” at the release of V5 (as known at this time).
Many forum users have left the V4 stable for quite some time now, and have not had major issues. In fact, I personally have had far fewer issues with the nightlies than I have had with the “stable” V4 releases; disclaimer: there have been a small number of some specific nightlies where there were obvious problems that were fixed right quickly after.
If one has a solid version control system in place it remains my opinion that is best for most KiCad users (without a mission critical V4 project in the works) to migrate to V5 with the one of the current RC3 nightly builds.
2 Likes
I have been running Debian Testing (Buster) for a spell now just to “test drive” RC2 and RC3.
I too have had good luck with them. This evening opted to move back to Stable while I await the official v5 release.
Being an Eagle CAD user (soon to be KiCAD user), I have been keeping an eye on this since January. I can’t wait to convert my 100 or projects to v5.
Very exciting news!
Cheers
Chris
I don’t expect any major changes before release now.
As always BACK UP YOUR PROJECT before any upgrade.
Strange. Yesterday (or the day before that depending on your time zone) Wayne wrote something about 20th of july.
Would really have been nice to have some warning time to be honest.
Anyone know the difference in meaning between “tagged” and “release” in context of the upversion to KiCad V5?
I am curious though - being a Debian user of both Stable and Testing, I wonder if v5 will make it to the Stable branch. Might anyone know that? I suppose I should ask the folks that actually packaged it for Sid/Testing to be certain but if someone here knows, would appreciate knowing.
Cheers
Chris
My guess would be only as a backport.
1 Like
Tagging something is a term from git. It means giving a specific commit a “name”. For kicad this means that this particular commit will be the source for the v5.0.0 release. The official release will come once the packagers and documentation guys finished their work. (Or in one week whatever comes first.)
3 Likes
Tagged is a Git nomenclature that the specific code will be used to the official release. Because the KiCad development never stop and new changes (present in the nightly) can be unstable and can’t in the 5.0 stable release, also in this moment no new features or big changes will be made on 5.0, only in the nightly (that we expect to be present at v6.0).
Today I saw some movimentation on https://bugs.launchpad.net/kicad closing old bug already fixed but that still opened. As @Rene_Poschl said, just missing some documentations, I think.
If you search GitHub, Master seems to have frozen, but there is also a 5.1 branch, which is moving ahead. as you would expect.
What is not clear is what Windows Nightly 16th July is.
1 Like
Nightlies always come from the “master” branch.
There are RC3 binaries in the testing directory as well, final binaries will turn up in the stable directory when the release is done.
We currently don’t build binaries from the 5.1 branch. We probably could, but there is already an annoying level of duplication in the build system.
2 Likes
A pity as a 5.1 preview is more immediately useful for near term fixes and improvements.
I would even suggest that V6 should drop 32 bit support. It would be interesting to know the ratio of 32 to 64 bit downloads now, but by the time V6 comes out Windows XP and Intel 32 bit Atoms will be a fading memory.