[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14140408#comment-14140408 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1626188 from [~thetaphi] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1626188 ] LUCENE-5944: Remove the version constant. The problem was the broken logic in TestBackwardsCompatibility to detect Lucene trunk which has an additional unreleased index before Version.LATEST: I will open issue, maybe Ryan has better idea. 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. Here is the proposal what to do in this issue: [http://mail-archives.apache.org/mod_mbox/lucene-dev/201409.mbox/%3CCAOdYfZUpAbYp-omdw=ngjsdzbkvhn2zydobzvj1gdxk+lrt...@mail.gmail.com%3E] -- 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14140893#comment-14140893 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1626277 from [~thetaphi] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1626277 ] LUCENE-5944: Fix building TAR with solr WAR (merge error) 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. Here is the proposal what to do in this issue: [http://mail-archives.apache.org/mod_mbox/lucene-dev/201409.mbox/%3CCAOdYfZUpAbYp-omdw=ngjsdzbkvhn2zydobzvj1gdxk+lrt...@mail.gmail.com%3E] -- 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138771#comment-14138771 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1625934 from [~rcmuir] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1625934 ] LUCENE-5944: move trunk to 6.x, create branch_5x 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 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138823#comment-14138823 ] Uwe Schindler commented on LUCENE-5944: --- I renamed all Jenkins Jobs and changed them to use other branch. We now also need to rename the JIRA version and add the new 5.0 to all additional backported issues. 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 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138834#comment-14138834 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1625946 from [~thetaphi] in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1625946 ] LUCENE-5944: delete old branch_4x 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 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138842#comment-14138842 ] Uwe Schindler commented on LUCENE-5944: --- OK: - I renamed JIRA Version 4.11 to 5.0 - I renamed JIRA version 5.0 to 6.0 For all additional backports from trunk to 5.x, we should add the 5.0 JIRA fix version. 4.11 is gone. branch_4x is gone, too, please SVN switch branch_4x to branch_5x. We now must bump the version numbers in the build files. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138919#comment-14138919 ] Shalin Shekhar Mangar commented on LUCENE-5944: --- Why did we delete branch_4x? When did we vote on not releasing 4.x anymore? 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138925#comment-14138925 ] Robert Muir commented on LUCENE-5944: - I opened this issue 6 days ago and nobody objected. we can't support any more 4.x releases in lucene anymore. Each release is plagued by corruptions in the back compat support. Its just not sustainable. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138927#comment-14138927 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1625976 from [~thetaphi] in branch 'dev/trunk' [ https://svn.apache.org/r1625976 ] LUCENE-5944: Bump version in trunk 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138969#comment-14138969 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1625980 from [~thetaphi] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1625980 ] LUCENE-5944: Bump version in branch_5x 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138971#comment-14138971 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1625983 from [~thetaphi] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1625983 ] LUCENE-5944: Bump Maven POM in branch_5x 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138986#comment-14138986 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1625990 from [~thetaphi] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1625990 ] LUCENE-5944: Remove useless test (will be fixed soon by LUCENE-5952) 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138988#comment-14138988 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1625991 from [~thetaphi] in branch 'dev/trunk' [ https://svn.apache.org/r1625991 ] LUCENE-5944: Remove useless test (will be fixed soon by LUCENE-5952) 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138998#comment-14138998 ] Tommaso Teofili commented on LUCENE-5944: - bq. I opened this issue 6 days ago and nobody objected. we can't support any more 4.x releases in lucene anymore. Each release is plagued by corruptions in the back compat support. Its just not sustainable. while I agree with the backcompat trouble it's still not acceptable to just move forward without a vote IMHO, even if the issue has been open for 6 days, there must be explicit consensus on things like moving to major releases. It's like saying that since java 7 will go EOL shortly we just move to java 8 without voting. To make it clear I would've voted +1 for the move, just I don't like the way it's been done. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139018#comment-14139018 ] Robert Muir commented on LUCENE-5944: - I didnt propose any release yet :) 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139041#comment-14139041 ] Steve Rowe commented on LUCENE-5944: I agree with Tommaso: there should have been a vote for this. Lazy concensus is the wrong model for big stuff like no more 4.x releases. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139054#comment-14139054 ] Uwe Schindler commented on LUCENE-5944: --- Hi, there is still a release 4.10.1 underway (Mike will just commit one more issue soon). In general there is no problem in releasing 4.10.2 quite soon, too. The fact we agreed on was to move to a new backwards model, because the current model prevents us from working effectively. So I don't see a 4.11 release coming anymore. Robert and I added a lot of news for a coming 5.0, which we will hopefully start as RC quite soon (after a few weeks of fine-tuning). The new version will still be able to read 4.x indexes, but 3.x gets removed. The branch_4x branch was removed because commit to 4.x should now only go through 4.10 branch and all work for 5.0 will go to branch_5x. The whole thing was just a rename of branch. Both branches coexisted for a short time to be able to get Jenkins servers up-to-date. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139058#comment-14139058 ] Robert Muir commented on LUCENE-5944: - All I did was create a branch in svn. If you want to restore 4.x branch and keep doing 4.x releases, thats ok with me. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139060#comment-14139060 ] Steve Rowe commented on LUCENE-5944: bq. The fact we agreed on was to move to a new backwards model, because the current model prevents us from working effectively. We? agreed? Where? 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139063#comment-14139063 ] Uwe Schindler commented on LUCENE-5944: --- LUCENE-5940 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139068#comment-14139068 ] Steve Rowe commented on LUCENE-5944: Seriously, Uwe? Robert opens an issue, 4 people comment on it, and that's we and agree? Again, lazy concensus is the wrong model for big stuff like this. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139071#comment-14139071 ] Robert Muir commented on LUCENE-5944: - I think thats enough to create a branch? thats all it is. Maybe if i named the branch lucene_5944 it would be less controversial? 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139084#comment-14139084 ] Yonik Seeley commented on LUCENE-5944: -- bq. Maybe if i named the branch lucene_5944 it would be less controversial? Yes, tha'ts a huge difference. Then it would not officially be trunk that is 6x and then no one would be forced to commit to 6x, and backport to 5x *and* 4x (assuming we want to continue the 4x line). 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139090#comment-14139090 ] Steve Rowe commented on LUCENE-5944: bq. I think thats enough to create a branch? thats all it is. When you name branches in a way that controls commits, and delete the branch on which up till now the next release was to be based, it's more than branch creation. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139095#comment-14139095 ] Robert Muir commented on LUCENE-5944: - I didnt delete any branch or control anyone's commits. I just did an svn copy. As far as continuing the 4.x line, who will be responsible for the backwards compatibility of those indexes? The current situation is not sustainable. I don't see a lot of people jumping up and down to help out with 3.x index back compat issues. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139099#comment-14139099 ] Uwe Schindler commented on LUCENE-5944: --- If somebody wants to restore 4.11, please revert my commits. Thanks. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[
https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139125#comment-14139125
]
Uwe Schindler commented on LUCENE-5944:
---
If you got hit by a 404 not found on committing to branch_4x:
{noformat}
$ svn switch https://svn.apache.org/repos/asf/lucene/dev/branches/branch_5x .
$ svn up
$ svn commit -m ...
{noformat}
If the branch would not be removed, you would have committed to the old one
instead, so this was to help you.
Unfortunately, I was commiting the removal just for you.
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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139130#comment-14139130 ] Uwe Schindler commented on LUCENE-5944: --- Robert: bq. Since there were no objections, I will do the svn move today. Uwe: bq. could you svn copy the branch, so I have some time to change Jenkins? After I reconfigured all jobs, I will delete the branch. An svn move is in fact just a copy + delete. Otherwise I am fine with the plan. I will also heavy commit backports together with you! 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139150#comment-14139150 ] Anshum Gupta commented on LUCENE-5944: -- This is certainly not how I thought Lucene/Solr 5.0 be! Historically, trunk has been used to cut a major release but with this, I wonder when would the code in trunk (that already exists, and is different from 4x (now 5x)) be released. 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139152#comment-14139152 ] Robert Muir commented on LUCENE-5944: - I am currently backporting everything to the branch except the controversial stuff that would slow releases e.g. mentioned by shawn heisey on the java 8 thread (means keeping the solr war etc so its not bogged down by that). 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139164#comment-14139164 ] Ryan Ernst commented on LUCENE-5944: bq. I wonder when would the code in trunk (that already exists, and is different from 4x (now 5x)) be released. When 6.0 is released? Part of the reason for this is a lot of very scary changes that were being backported into 4.11, that should have been in a major release. Having a tighter backcompat policy in the future (now starting with 6.x I guess) would help us do releases more quickly (IMO, around every year or a little more). See LUCENE-5940 that Uwe mentioned earlier here. Simply releasing 5.0 from trunk would have been more controversial (probably) since it has a lot of changes that still need to be cleaned up (StoredDocument/IndexedDocument, what happens with solr war/nowar, etc). 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139242#comment-14139242 ] Robert Muir commented on LUCENE-5944: - I'm not proposing to release anything anytime soon. I just want to branch and work on a 5.x branch (for maybe months out, whatever), that does not have the crazy 3.x backwards compatibility, only requires java 7 (but maybe some breaking changes like NIO.2), and so on. Meanwhile trunk can be java 8 and have all that fun, but we can't sit here and lie to ourselves that we can continue to issue 4.x minor releases: we cannot support the index backwards compatibility. Every single recent 4.x release has serious corruption issues due to 3.x support: I am seeing these on a near daily basis. with the most recent release, lucene is even corrupting 4.x indexes because of the complexity of 3.x support. its not just a finite set of bugs for us to fix, its just too much complexity. And we shouldn't make 5.0 require java 8... but at the same time developers who want to use java 8 features can have trunk to do that. 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. Here is the proposal what to do in this issue: [http://mail-archives.apache.org/mod_mbox/lucene-dev/201409.mbox/%3CCAOdYfZUpAbYp-omdw=ngjsdzbkvhn2zydobzvj1gdxk+lrt...@mail.gmail.com%3E] -- 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139373#comment-14139373 ] ASF subversion and git services commented on LUCENE-5944: - Commit 1626055 from [~rcmuir] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1626055 ] LUCENE-5944: backport changes to branch_5x, except in-flux changes (o.a.l.document change, removal of solr .war), plus merge changes entries, plus fix solr precommit, plus fix docs, plus keep standardtokenizer 4.0 grammar for back compat 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. Here is the proposal what to do in this issue: [http://mail-archives.apache.org/mod_mbox/lucene-dev/201409.mbox/%3CCAOdYfZUpAbYp-omdw=ngjsdzbkvhn2zydobzvj1gdxk+lrt...@mail.gmail.com%3E] -- 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138180#comment-14138180 ] Robert Muir commented on LUCENE-5944: - Sorry, i was slow, i was debugging a test failure. I will do this tonight (svn copy). I am a little worried about keeping branch_4x open, because people may still commit to it. But I don't want to drive jenkins haywire. So I will just watch the commits list. 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 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14135444#comment-14135444 ] Robert Muir commented on LUCENE-5944: - Since there were no objections, I will do the svn move today. 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 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14135901#comment-14135901 ] Uwe Schindler commented on LUCENE-5944: --- Hi, could you svn copy the branch, so I have some time to change Jenkins? After I reconfigured all jobs, I will delete the branch. An svn move is in fact just a copy + delete. Otherwise I am fine with the plan. I will also heavy commit backports together with you! 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 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
[jira] [Commented] (LUCENE-5944) move trunk to 6.x, create branch_5x
[ https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14135908#comment-14135908 ] Uwe Schindler commented on LUCENE-5944: --- OK, I disabled Policeman Jobs. ASF Jenkins will need a lot of time to run 2 more trunk jobs, so its unlikely that it breaks soon. Go ahead! 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 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
