kicad-developers team mailing list archive

[Cirilo Bernardo <cirilo.bernardo@xxxxxxxxx>]

On Fri, Feb 19, 2016 at 11:57 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx>
wrote:

> I just checked and the library has been tagged with 4.0.2 but there were
> changes to device.lib since 4.0.1.  It looks like the POT component was
> resized which most likely will fire a component recovery for users who
> have POTs in their schematics.  I think we should ship component
> libraries that do not trigger a recovery during the 4 series stable
> releases so it looks like you should pull the 4.0.1 library for
> packaging for the remainder of version 4 stable releases.  I'll see if I
> can come up with a reasonable policy to eliminate confusion in the
> future.  We probably should just tag the library at X.0.0 when the
> stable version is released and use that for the entire stable release
> series to prevent any surprises for the user.  The other option is to
> create separate library packages and let the user assume the risk when
> updating the libraries.
>


I'm in favor of using a single library tag for an entire Stable release
series. For me the only acceptable changes, as is the case for software, is
if a component was wrong and later fixed. As in the case of software, any
fixes to erroneous components must be done via a branch and patch.
Due to the large number of files and rapid additions and changes, this
quickly becomes a nightmare unless someone wants to create a
meta-repository to pull in *all* tagged libraries and then only update
components which have been fixed.

- Cirilo



>
> On 2/19/2016 1:39 AM, Nick Østergaard wrote:
> > I need a clear answer. If we don't want to update, then we shall move
> > the tag on the libs to the 4.0.1 tag on the libs.
> >
> > 2016-02-15 19:36 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> >> I'm not sure how much of a difference it makes with the github libraries
> >> since the contents of the libraries can change even if you don't update
> >> your fp-lib-table.  Shipping the updated fp-lib-table wont make any
> >> difference unless the user chooses to copy the new one.  The schematic
> >> libraries however are a different matter.  We should probably keep those
> >> the same through out the entire stable 4 release series rather than
> >> breaking users schematics.  I know Chris's rescue code goes a long way
> >> in mitigating this issue but I would still like to avoid users having to
> >> rescue a schematic during a stable release series.
> >>
> >> On 2/15/2016 1:29 PM, Carl Poirier wrote:
> >>> The pretty repository with the old name still exists for as long as
> >>> needed. My question is about having lib differences between bugfix
> >>> releases. In this case, the fp-lib-table will be updated so that 4.0.3
> >>> will use the renamed lib whereas 4.0.2 uses the old lib.
> >>>
> >>> Regards,
> >>>
> >>> Carl
> >>>
> >>> On Mon, Feb 15, 2016 at 2:40 AM, Nick Østergaard <oe.nick@xxxxxxxxx
> >>> <mailto:oe.nick@xxxxxxxxx>> wrote:
> >>>
> >>>     2016-02-14 17:07 GMT+01:00 Carl Poirier <carl.poirier.2@xxxxxxxxx
> >>>     <mailto:carl.poirier.2@xxxxxxxxx>>:
> >>>     > We have some new libraries to add to the fp-lib-table and one to
> rename. If
> >>>     > we do so now, when we'll be tagging 4.0.3, it will include the
> changes.
> >>>     >
> >>>     > Would this be permitted in such a release? If not, what about
> version 4.1?
> >>>
> >>>     I am not exactly sure, but what about we just do not perform the
> >>>     rename (for the release), but just add the new ones, then there is
> >>>     little change for the user to experience errors, or am I mistaken?
> >>>
> >>>     > On Sun, Feb 14, 2016 at 7:10 AM, Nick Østergaard
> >>>     <oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx>> wrote:
> >>>     >>
> >>>     >> 2016-02-14 12:18 GMT+01:00 Nick Østergaard <oe.nick@xxxxxxxxx
> >>>     <mailto:oe.nick@xxxxxxxxx>>:
> >>>     >> > Ok, so we tag the latest snapshot of the libraries as
> suggested
> >>>     by the
> >>>     >> > librarians, and will do the same with the docs to get the
> >>>     latest fixes
> >>>     >> > and translations there too.
> >>>     >> >
> >>>     >> > Wayne, I wonder why you tagged the release kicad-4.0.2 instead
> >>>     of just
> >>>     >> > 4.0.2 as you did for 4.0.0 and 4.0.1.
> >>>     >>
> >>>     >> Hmm, I think that is just a name set in the lp web ui, which
> can be
> >>>     >> edited.
> >>>     >>
> >>>     >> > 2016-02-13 22:59 GMT+01:00 Wayne Stambaugh
> >>>     <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>>:
> >>>     >> >> Did we tag 4.0.1?  I thought we just tagged 4.0 and used it
> >>>     for 4.0.1
> >>>     >> >> but I'm not sure.  I don't think the docs have any of the new
> >>>     stuff
> >>>     >> >> like
> >>>     >> >> the one button board update yet so it may be OK to tag the
> >>>     docs 4.0.2.
> >>>     >> >>
> >>>     >> >> On 2/13/2016 4:56 PM, Nick Østergaard wrote:
> >>>     >> >>> I expect we tag a new snapshot of the libraries and docs
> again.
> >>>     >> >>>
> >>>     >> >>> 2016-02-13 22:51 GMT+01:00 Wayne Stambaugh
> >>>     <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>>:
> >>>     >> >>>> Just a heads up, stable version 4.0.2 has been released.
> >>>     This is a
> >>>     >> >>>> bug
> >>>     >> >>>> fix release so when the build devs get a chance, please
> >>>     create builds
> >>>     >> >>>> for the new stable release packages.  Thank you everyone
> for
> >>>     your
> >>>     >> >>>> efforts to make this possible.
> >>>     >> >>>>
> >>>     >> >>>> Cheers,
> >>>     >> >>>>
> >>>     >> >>>> Wayne
> >>>     >> >>>>
> >>>     >> >>>> _______________________________________________
> >>>     >> >>>> Mailing list: https://launchpad.net/~kicad-developers
> >>>     >> >>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >>>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>     >> >>>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>>     >> >>>> More help   : https://help.launchpad.net/ListHelp
> >>>     >> >>
> >>>     >>
> >>>     >> _______________________________________________
> >>>     >> Mailing list: https://launchpad.net/~kicad-developers
> >>>     >> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >>>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>     >> Unsubscribe : https://launchpad.net/~kicad-developers
> >>>     >> More help   : https://help.launchpad.net/ListHelp
> >>>     >
> >>>     >
> >>>
> >>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>