[
https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550399#comment-13550399
]
Steve Rowe commented on LUCENE-4134:
------------------------------------
bq. Wouldn't another alternative instead just continue to use our p.a.o/~
versus deploying to two places?
Yes, you're right: +1
bq. Then we can discuss/iterate on other changes to the release process at our
leasiure (ie: maybe we put hte RCs in svn, and tweak the directory structure so
a simple "svn mv" works for the dist files, and we have some other script for
the maven files)
If the {{maven/}} directories weren't there, a simple "svn mv" would work - no
other tweaking required.
What "other script" did you have in mind for the maven files? Are you talking
about the need to change the smoke tester if the maven artifacts are moved out
of the RC?
> modify release process/scripts to use svn for rc/release publishing
> (svnpubsub)
> -------------------------------------------------------------------------------
>
> Key: LUCENE-4134
> URL: https://issues.apache.org/jira/browse/LUCENE-4134
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Hoss Man
> Priority: Blocker
> Fix For: 4.1
>
>
> By the end of 2012, all of www.apache.org *INCLUDING THE DIST DIR* must be
> entirely managed using "svnpubsub" ... our use of the Apache CMS for
> lucene.apache.org puts us in compliance for our main website, but the dist
> dir use for publishing release artifacts also needs to be manaved via svn.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
