What do people thing about waiting to cut the branch until someone has something that shouldn't go into 6.0? Committing will be easier that way.
No biggie, maybe Mike's purpose is served by the notice "get your stuff in trunk that you want to go in 6.0 Real Soon Now" ;) As always, since I'm not volunteering to be the RM, I'll be happy with whatever people decide.... On Fri, Jan 8, 2016 at 7:51 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 1/8/2016 8:13 AM, Shawn Heisey wrote: >> I've only been paying attention to commits for one new major release, so >> I can offer some info on 5.0, but not any of the previous major releases. >> >> Robert created branch_5x on 2014/09/18. Version 5.0.0 was released on >> 2015/02/20. That's five months from new branch to new major release. > > Turns out I *do* have information in my email history for 4.x. Robert > created branch_4x on 2012/05/29. The 4.0.0 release was announced on > 2012/10/12 -- four and a half months later. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
