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 <apa...@elyograg.org> 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-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > -- Regards, Shalin Shekhar Mangar. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
