On 1/23/2018 11:56 AM, Matthijs Kooijman wrote:
> Hi Wayne,
>
>> I was not being sarcastic. Here is what I meant:
> Thanks for clarifying.
>
>> For stable version 5, the libraries should be tagged and used for all
>> stable 5 point releases (5.0.1, 5.0.2, ...). Most corporate users
>> prefer consistency over having the latest libraries so installing the
>> next point release of kicad will not change the libraries.
> Ok. Then my proposal does not apply at all to these users, since their
> libraries are completely unchanged within the (e.g.) v5 release cycle.
>
> My proposal *does* apply to users that:
> 1. Upgrade their libaries when upgrading from (e.g.) v5 to v6.
I agree, libraries should get updated for new stable release versions.
I think users expect this to happen.
> 2. Upgrade their libraries ("at their discretion") within the (e.g.) v5
> cycle.
>
> Even though in both cases, it is certainly acceptable to have uses
> expect some disruption in their library organisation (e.g. symbols that
> changed in a non-compatible manner, moving pins around), it would also
> be nice if these upgrades could be as smooth as possible (removing the
> need to manually figure out what changes were made to the library
> filenames and what symbols were moved where).
This is not a trivial issue to fix. I'm not sure there is a good answer
for this issue.
>
> Also, users from #2 are also beta-testing library changes, which
> improves the libaries seem by the #1 users, which seems like an
> additional reason to make it easier to upgrade often.
>
> Gr.
>
> Matthijs
>
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
