It’s been in for a bit but probably worth a mention: The routing corner style (Ctrl+/) now has 4 modes to cycle through: 45-degree, 45-degree with rounded corners, 90-degree, and 90-degree with rounded corners. The active corner style is shown in the message panel at the bottom while routing.
Sad news for those who have waited for the new python API. In Python API status in v6 we have been told that it’s not ready yet for v6 RC or relase and will be postponed. Existing plugins should be converted to the changed old style API to work with v6. There will be no eeschema API in v6. More details and discussion in the linked thread.
The router operates in a fixed-angle mode, not fixed-radius. You set the radius by where you click. Fixed-radius curves can be added using the Fillet Tracks post-processing operation.
As many of you have already seen, the development version has moved to 6.0RC1 phase.
Bug fixing will continue. The new version string is seen in some places. You will get the settings migration dialog, so there will be both 5.99 (old) and 6.0 (new) folders in the user specific kicad configuration. The configuration system is identical between the last 5.99 and first RC1 commit, but you can consider starting from scratch at this point to get a fresh feeling. If someone jumps in now from 5.1, I personally recommend starting from scratch.
Also if you download a “lite” build of nightly MSVC right now, you will end up missing libraries because it will install to \6.0\ but without any libraries because its “lite”.
tl;dr you can now invoke pip to install packages for kicad on windows easily without admin right escalation. pip packages get installed to C:\Users<username>\Documents\KiCad\6.0\3rdparty\python39\site-packages
Wayne has just tagged version 6.0.0-rc2. We believe this to be the version that will become v6 but due to having made a lot of bug fixes to the code since 6.0.0-rc1, we’d like to get more testing done before we finally tag 6.0.0 in case there are any final critical bugs that should be addressed before release.
We are now in a soft code freeze where only critical and high priority bug fixes will be addressed and only after code review by two other lead developers.
If no critical/high priority bugs are open on Monday morning (20-Dec), 6.0.0 will be tagged then and the packaging process can begin.
Please download the latest nightly and use it as much as you can, reporting any issues encountered (in particular any crashes or data loss) by going to Help->Report bug (you will need to create a gitlab account in order to report any issues).
Am I correct in assuming that this discussion will present a notice when 6.0 is posted as the stable release? Whoever replies next to this discussion will have the honor of post number 400.