lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas Knize <nkn...@gmail.com>
Subject Re: Lucene/Solr 6.0.0 Release Branch
Date Thu, 03 Mar 2016 15:07:32 GMT
Since this is the first major release since cutting over to git the intent
was to first create the 6x branch and create 6_0 once Jenkins was stable
with the new branches (version changes, backcompat, etc). This meant
a slight gap between creating the 6x and 6_0 branch, and a temporary
feature freeze until everything checks out.

That being said, if everyone is comfortable with the current state of
Jenkins (I know Mike did a lot of work to ensure backcompat tests pass) I
have no problem with the creation of the 6_0 branch. We just needed to give
enough time for things to settle and people to respond.

- Nick

On Thursday, March 3, 2016, Shalin Shekhar Mangar <shalinmangar@gmail.com>
wrote:

> Hmm I think I created the branch without pulling the latest code. I'll fix.
>
> On Thu, Mar 3, 2016 at 6:41 PM, Robert Muir <rcmuir@gmail.com
> <javascript:;>> wrote:
> > This is missing a bunch of yesterday's branch_6x changes. Some of
> > david smiley's spatial work, at least one of my commits.
> >
> > On Thu, Mar 3, 2016 at 5:10 AM, Shalin Shekhar Mangar
> > <shalinmangar@gmail.com <javascript:;>> wrote:
> >> FYI, I have created the branch_6_0 so that we can continue to commit
> >> stuff intended for 6.1 on master and branch_6x. I have also added the
> >> 6.1.0 version on branch_6x and master.
> >>
> >> On Wed, Mar 2, 2016 at 9:51 PM, Shawn Heisey <apache@elyograg.org
> <javascript:;>> wrote:
> >>> On 3/2/2016 4:19 AM, Alan Woodward wrote:
> >>>> Should we create a separate branch_6_0 branch for the feature-freeze?
> >>>>  I have stuff to push into master and that should eventually make it
> >>>> into 6.1, and it will be easy to forget to backport stuff if there's
a
> >>>> week before I can do that…
> >>>
> >>> +1
> >>>
> >>> When I saw Nick's email about branch_6x being feature frozen, my first
> >>> thought was that we don't (and really can't) feature freeze the stable
> >>> branch -- isn't new feature development (for the next minor release in
> >>> the current major version) the entire purpose of branch_Nx?
> >>>
> >>> A feature freeze on a specific minor version does make sense.  I've
> seen
> >>> a couple of people say that we have, but there are also a few messages
> >>> from people saying that they want to include new functionality in 6.0.
> >>> I expect that backporting almost anything from branch_6x to branch_6_0
> >>> will be relatively easy, so it may be a good idea to just create the
> new
> >>> branch.
> >>>
> >>> Thanks,
> >>> Shawn
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> <javascript:;>
> >>> For additional commands, e-mail: dev-help@lucene.apache.org
> <javascript:;>
> >>>
> >>
> >>
> >>
> >> --
> >> Regards,
> >> Shalin Shekhar Mangar.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> <javascript:;>
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> <javascript:;>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <javascript:;>
> > For additional commands, e-mail: dev-help@lucene.apache.org
> <javascript:;>
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@lucene.apache.org <javascript:;>
>
>

Mime
View raw message