kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #25645
Re: 4.0.3 stable release last call.
My bad. I thought this patch was part of a bug report. I'll commit it
and change the 4.0.3 tag. This is the last non-critical bug fix for
4.0.3. Any other non-critical bugs can wait until the 4.0.4 release.
On 8/3/2016 2:15 PM, Nick Østergaard wrote:
> I don't think it has been reported on the tracker, but that doesn't mean
> it is not a bug ;)
>
>
> Den 03/08/2016 18.01 skrev "Wayne Stambaugh" <stambaughw@xxxxxxxxx
> <mailto:stambaughw@xxxxxxxxx>>:
>
> I got that but Nick mentioned a bug fix so I assumed that it fixed a bug
> report. Did r7000 fix a bug report or not? If so, what is the bug
> report number so I can link to it when I commit the stable release fix.
>
> On 8/3/2016 11:52 AM, Chris Pavlina wrote:
> > He's referring to revision 7000.
> >
> > On Wed, Aug 03, 2016 at 11:41:36AM -0400, Wayne Stambaugh wrote:
> >> Which bug does it fix? It is not linked in the commit and I did
> a quick
> >> search and I cannot find the bug in question.
> >>
> >> A reminder to my devs with commit access, please use the bzr --fixes
> >> option when committing LP bug report fixes so I don't have to go back
> >> and figure out which commit fixes which bug.
> >>
> >> On 8/3/2016 9:17 AM, Nick Østergaard wrote:
> >>> Hi Wayne
> >>>
> >>> Will it be possible to include the fix the the F.Silk on new
> pads too?
> >>> I know it is not a segfault or anything similar, but I still
> consider
> >>> it a bugfix.
> >>>
> >>>
> http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/7000
> >>>
> >>> 2016-08-03 14:33 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx
> <mailto:stambaughw@xxxxxxxxx>>:
> >>>> If no one has any issues, I'm going to apply this patch to the
> stable
> >>>> branch an tag r6298 as 4.0.3 instead of r6297. I am still
> planning on
> >>>> announcing the stable release over the weekend. Let me know if
> this is
> >>>> going to be a problem and I will push the stable release back
> another
> >>>> week. I'm guessing this will only effect our package devs.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Wayne
> >>>>
> >>>> On 8/2/2016 7:00 PM, Nick Østergaard wrote:
> >>>>> Hi
> >>>>>
> >>>>> Please be aware of this bug which causes a segfault. The issues
> >>>>> appears both on recent product and 4.0.2.
> >>>>> https://bugs.launchpad.net/kicad/+bug/1607430
> >>>>>
> >>>>> The reason have been found, but I am not sure if you would
> consider
> >>>>> the fix for inclusion in 4.0.3 at this stage.
> >>>>>
> >>>>> Nick
> >>>>>
> >>>>> 2016-07-09 18:07 GMT+02:00 Wayne Stambaugh
> <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>>:
> >>>>>> I'm making one last call for any last bug fixes for the
> version 4 stable
> >>>>>> branch before I tag 4.0.3. If you are working on anything or
> know of
> >>>>>> anything that could be a show stopper, please let me know. I
> hope to
> >>>>>> tag 4.0.3 early next week to give our doc devs and
> translators a chance
> >>>>>> to make any last changes before I roll out 4.0.3 and make the
> announcement.
> >>>>>>
> >>>>>> 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
>
Follow ups
References