[
https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550352#comment-13550352
]
Steve Rowe edited comment on LUCENE-4134 at 1/10/13 8:09 PM:
-------------------------------------------------------------
bq. [A]s part of this new process there will also be a
"https://dist.apache.org/repos/dist/dev/lucene"; directory where release
candidates can be put for review (instead of
people.apache.org/~releasemanager/...), and if/when they are voted successfully
a simple "svn mv" to dist/release/lucene makes them official and pushes them to
the mirrors.
There is a wrinkle here: maven artifacts. Our current process includes them
with the ASF release artifacts at the RC review download link. If we continue
this when we instead commit RCs to
{{repos/dist/dev/lucene/\{java,solr}/X.Y.ZRCN-rMMMMMMM/}}, then the release
publishing process can't be just {{svn mv
dev/lucene/\{java,solr}/X.Y.ZRCN-rMMMMMMM release/lucene/\{java,solr}/X.Y.Z}}.
Instead, we'll have to somehow exclude the maven artifacts, e.g. {{svn rm
dev/lucene/\{java,solr}/X.Y.ZRCN-rMMMMMMM/maven}}.
An alternative: now that we stage maven artifacts to Nexus
(repository.apache.org) prior to the release, we could as part of an RC
announcement also include the Nexus link, and not include the maven artifacts
in {{repos/dist/dev/lucene/}}. This option gets my +1.
was (Author: steve_rowe):
bq. [A]s part of this new process there will also be a
"https://dist.apache.org/repos/dist/dev/lucene"; directory where release
candidates can be put for review (instead of
people.apache.org/~releasemanager/...), and if/when they are voted successfully
a simple "svn mv" to dist/release/lucene makes them official and pushes them to
the mirrors.
There is a wrinkle here: maven artifacts. Our current process includes them
with the ASF release artifacts at the RC review download link. If we continue
this when we instead commit RCs to
{{repos/dist/dev/lucene/{java,solr}/X.Y.ZRCN-rMMMMMMM/}}, then the release
publishing process can't be just {{svn mv
dev/lucene/{java,solr}/X.Y.ZRCN-rMMMMMMM release/lucene/{java,solr}/X.Y.Z}}.
Instead, we'll have to somehow exclude the maven artifacts, e.g. {{svn rm
dev/lucene/{java,solr}/X.Y.ZRCN-rMMMMMMM/maven}}.
An alternative: now that we stage maven artifacts to Nexus
(repository.apache.org) prior to the release, we could as part of an RC
announcement also include the Nexus link. This option gets my +1.
> 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]
