[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139195#comment-14139195 ]
Anshum Gupta commented on LUCENE-5944: -------------------------------------- I understand the back-compat issue but honestly, people working on Solr side of things have stuff in trunk that they wanted to release as part of the next non-backcompat release (major release). I, and I'll assume others too, had more things planned for the 5.0 release. With none of that happening with 5.0 and users getting a back-compat breaking release there, it'd be bad for the users to receive another release that's reasonably different, and breaks API's just a few months after 5.0 goes out. I'm proposing that we work together to have releases (and release numbers) that sound reasonable to the users (and developers). > move trunk to 6.x, create branch_5x > ----------------------------------- > > Key: LUCENE-5944 > URL: https://issues.apache.org/jira/browse/LUCENE-5944 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Robert Muir > Fix For: 5.0 > > > In order to actually add real features (as opposed to just spending 24/7 > fixing bugs and back compat), I need a trunk that doesn't have the back > compat handcuffs. > In the meantime, we should rename the current trunk (which is totally tied > down in back compat already, without even a single release!) to branch_5x > while you guys (i wont be doing any back compat anymore) figure out what you > want to do with the back compat policly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org