Just to be sure i will ask the other librarians how strict they where
with our policy. (Sadly on the symbol side git is not of much help so i
really need to rely on their word. I will also make some manual checks.)
For the future we might think about getting check scripts developed that
check for changes that would go too far. (To reduce the chance of human
errors. Some maintainers might be tempted to include one small change
that is slightly across the line. If this happens with enough frequency
then the sum of all changes could be too much.)
On 28/08/18 19:16, Wayne Stambaugh wrote:
On 8/28/2018 12:48 PM, Rene Pöschl wrote:
Right now we have no changes made that would break projects. (That is
what i meant with "backwards compatibility" I know it is not quite the
right term)
Also i thought the cache lib plus rescue dialog should take care of
minor changes to symbols if the user does not want to update a symbol
should it be changed.
Yes, but I do not like depending on the cache. It's too fragile. Once
the new schematic file format is in place, this will no be an issue.
Until then, I prefer to error on the side of caution given the cache
issues we've had in the past.
It should not even be necessary as we do not allow changes to symbol pin
numbers or positions. (Unless there was a mistake in the symbol.)
As we did not include any of the wrongly scaled or wrongly aligned 3d
models in the version 5 library there is also no danger of damaging the
3d rendering side. (There is a reason why the version 5 3d model library
is a lot smaller compared to the version 4 3d model lib)
We do neither allow changing any library names nor do we change symbol,
footprint or 3d model names unless the original name was wrong enough to
be in danger of being confused with a part different to the one that the
object really represents.
If you do not intend to include the library then i will lift the ban on
major changes as it does not make any sense in that case to hold back.
(The only reason would be to allow including bugfixes into future kicad
bugfix releases. I would include updating to newer industry standards as
bugfix. The later is the main work being continued on the footprint
side. We simply where not done with it with the v5 release but it was
not bad enough to postpone the release.)
I didn't realize you were keeping tight control of the library commits.
I'm fine with these changes being added to 5.0.1. I would like to keep
the libraries relatively stable during the entire 5 stable series. For
version 6, you can make whatever changes you see fit.
On 28/08/18 18:30, Wayne Stambaugh wrote:
I would be careful with any library improvements during stable bug fix
releases, particularly for symbol and 3d model libraries which are
linked rather than embedded. My preference would be to just use the
same libraries tagged for the 5.0.0 release to keep changes to user
designs to a minimum. Users can always download the latest libraries if
they prefer the bleeding edge.
On 8/28/2018 12:18 PM, Rene Pöschl wrote:
Is it planned to include a new version of the libraries as well?
Right now we ensure that the library is relatively stable so i think the
improvements made since the v5 release can easily be included.
(We do not allow major changes that would break backward compatibility.
My plan is to use this rule at least till after the 5.1 release. Maybe
even until the new file format is well enough implemented to play around
with it in the official library.)
On 27/08/18 21:38, Wayne Stambaugh wrote:
I would like to get the 5.0.1 release out by the end of September if at
all possible. There are still a few open bug reports which need to be
fixed before we can release this so if you can fix any of the ones that
do not already have an assignee[1], any help would be appreciated. My
goal is to have all of the bug reports closed by 9/15 and give the
package devs a few weeks before making the release announcement.
Cheers,
Wayne
[1]: https://launchpad.net/kicad/+milestone/5.0.1
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp