I created the new series on Lauchpad a few hours ago.  I still have to
decide whether to link it to the product branch or make it a separate
source branch.  I'm still trying to wrap my head around it as well as
get these last few dialog fixes committed.

On 9/12/2015 3:33 PM, Jon Neal wrote:
> So I don't think it is Friday in any part of the world anymore.
> 
> Any update on the branch? :)
> 
> Jon
> 
> On Sat, Sep 12, 2015 at 12:18 PM, Nick Østergaard <oe.n...@gmail.com
> <mailto:oe.n...@gmail.com>> wrote:
> 
>     For your (and others) information, in the current moment of writing
>     this email, there are no more critical or high bugs on the tracker.
> 
>     2015-09-08 21:34 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com
>     <mailto:stambau...@gmail.com>>:
>     > I think the current situation is as good as we can hope for as far as
>     > blockers for rc1. I'm going to try to create a new version 4 stable
>     > release series on Launchpad Friday if no new show stoppers crop up.
>     > Periodically I will merge any bug fixes from the product branch
>     into the
>     > 4 stable series branch and increment the rc number. If we manage to go
>     > a few weeks with no new crash or data loss bugs, I will tag it a
>     stable
>     > release.
>     >
>     > On 9/8/2015 3:02 PM, Nick Østergaard wrote:
>     >> Wayne, was it your intention to include the incomplete bugs in the
>     >> blockers for rc1? I mean, incomplete bugs are bugs that have a
>     >> potential to be revived, but where the developers are not really
>     >> supposed to spend more time on them until some feedback are given.
>     >>
>     >> I personally don't think they should be included in that list,
>     even if
>     >> critical or high or not.
>     >>
>     >> 2015-09-06 22:11 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com
>     <mailto:stambau...@gmail.com>>:
>     >>> This is a reminder to *all* developers, please do not send any
>     patches
>     >>> or merge requests unless it is specifically to fix an existing bug
>     >>> report. Also, please don't bother fixing the build scripts or any of
>     >>> the CMake dependency library build code as they will be removed
>     during
>     >>> the next development cycle. My preference is that we focus on the
>     >>> critical bug reports that are keeping me from creating an rc1
>     branch.
>     >>> They can be found here:
>     >>>
>     >>>
>     
> https://bugs.launchpad.net/kicad/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
>     >>>
>     >>> This list needs to get to zero before I'm willing to create any
>     rc1 branch.
>     >>>
>     >>> Thank you for your cooperation.
>     >>>
>     >>> Cheers,
>     >>>
>     >>> Wayne
> 
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     Post to     : kicad-developers@lists.launchpad.net
>     <mailto: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

Reply via email to