Adrien: Right, thus my "if it's easy" clause ;)
I'm not suggesting at all that we go very far down this road, more "if it merges cleanly and makes sense, backport. Maybe. If you feel like it". And I'm _really_ not suggesting that we try to back-port anything that would make our lives harder, more "let's make 6x as complete as we can without making development too much more difficult". Erick On Tue, May 23, 2017 at 8:47 AM, Adrien Grand <jpou...@gmail.com> wrote: > Le mar. 23 mai 2017 à 17:15, Erick Erickson <erickerick...@gmail.com> a > écrit : >> >> Do others expect there to be a 6.7 release? I'm guessing there'll be a >> 6.7, and maybe one or two 6.7.x releases while 7.x settles down and/or >> we want to put a bow on the 6x code line. > > > Once 7.0 is out, releasing 6.x becomes trickier since we need to make sure > not only that it can read all previous versions, but also that new versions > (7.x) can read it. I'm not suggesting we do not do any release at all: we > should still do bugfix releases when important bugs are discovered. Since > bugfix releases tend to have contained change logs, it is easier to reason > about what could go wrong so we just need to be a bit more careful. However > I think we should avoid releasing new 6.x minor releases once 7.0 is out. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
