[ 
https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Rowe resolved LUCENE-4134.
--------------------------------

       Resolution: Fixed
         Assignee: Steve Rowe
    Lucene Fields:   (was: New)

INFRA-5739 has been resolved - svnpubsub for releases has been set up.  And it 
functioned properly for the 4.1 Lucene & Solr releases.

I've taken a first pass at modernizing the [Lucene 
ReleaseTodo|http://wiki.apache.org/lucene-java/ReleaseTodo] documentation,  
including a description of publishing by committing final release distributions 
to the {{dist.apache.org/repos/dist/releases/lucene/}} SVN repo.

I updated Mike McCandless's {{dev-tools/scripts/buildAndPushRelease.py}} script 
to run under Python 3.2 - otherwise it wouldn't run the smoke tester, which 
requires Python 3.2.  I used this script to build, push, and smoke test the RC. 
 It's very nice - it handles lots of tedious details for you.  The flip side of 
this is that what it does could become magic; my recommendation is to fully 
review the script before using it to make a real RC. 

I think enough progress was made here for now.  Further changes can be made via 
new issues.
                
> 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
>            Assignee: Steve Rowe
>            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]

Reply via email to