[
https://issues.apache.org/jira/browse/LUCENE-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2326:
----------------------------------
Fix Version/s: 3.1
Flex Branch
I think the ideal case for this would be that the backwards folder simply
contains the src-folder of the previous branch (after creation). No extra
folder like now in between, so it looks like "/backwards/src/...". After a
release, one would first "svn rm" the old and then "svn copy" the src folder of
the previously created release branch to trunk. I would add this to the release
todo.
On this change, all committers must first manually do a operating-system "rm
-rf" on the backwards folder by calling "ant clean-backwards" before svn up.
Maybe create a patch before :-)
> Remove SVN.exe and revision numbers from build.xml by svn-copy the backwards
> branch and linking snowball tests by svn:externals
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2326
> URL: https://issues.apache.org/jira/browse/LUCENE-2326
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: Flex Branch, 3.1
>
>
> As we often need to update backwards tests together with trunk and always
> have to update the branch first, record rev no, and update build xml, I would
> simply like to do a svn copy/move of the backwards branch.
> After a release, this is simply also done:
> {code}
> svn rm backwards
> svn cp releasebranch backwards
> {code}
> By this we can simply commit in one pass, create patches in one pass.
> The snowball tests are currently downloaded by svn.exe, too. These need a
> fixed version for checkout. I would like to change this to use svn:externals.
> Will provide patch, soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
