Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change 
notification.

The "HowToRelease" page has been changed by RobertMuir.
The comment on this change is: update trunk location.
http://wiki.apache.org/solr/HowToRelease?action=diff&rev1=58&rev2=59

--------------------------------------------------

   1. If this is the first release in a series (i.e. relase X.Y.0):
    1. create a branch for the series:
    {{{
- svn copy https://svn.apache.org/repos/asf/lucene/solr/trunk \
+ svn copy https://svn.apache.org/repos/asf/lucene/dev/trunk \
-   https://svn.apache.org/repos/asf/lucene/solr/branches/branch-X.Y -m 
"Starting Solr X.Y branch."
+   https://svn.apache.org/repos/asf/lucene/dev/branches/branch-X.Y -m 
"Starting Solr X.Y branch."
  }}}
    1. Create a new distribution directory: 
{{{people.apache.org:/www/www.apache.org/dist/lucene/solr/X.Y}}}
-  1. Check out the branch with:           {{{svn co 
https://svn.apache.org/repos/asf/lucene/solr/branches/branch-X.Y \}}}
+  1. Check out the branch with:           {{{svn co 
https://svn.apache.org/repos/asf/lucene/dev/branches/branch-X.Y \}}}
    . '''Note:''' at the moment releases need to be done on a unix box or in a 
cygwin environment with unix linefeeds, because fixcrlf is only done on the 
sources in the zip artifact
   1. Update the version numbers in common-build.xml on the branch:
    * specversion should be set to X.Y.M.${dateversion}, where X.Y.M is the 
release being made.
@@ -67, +67 @@

  
   1. Tag the release:
   {{{
- svn copy https://svn.apache.org/repos/asf/lucene/solr/branches/branch-X.Y \
+ svn copy https://svn.apache.org/repos/asf/lucene/dev/branches/branch-X.Y \
-    https://svn.apache.org/repos/asf/lucene/solr/tags/release-X.Y.M -m "Solr 
X.Y.M release."
+    https://svn.apache.org/repos/asf/lucene/dev/tags/release-X.Y.M -m "Solr 
X.Y.M release."
  }}}
   1. Copy release files to the distribution directory.
    1. {{{scp -p dist/apache-solr-X.Y.M.tar.gz* 
people.apache.org:/www/www.apache.org/dist/lucene/solr/X.Y}}}
@@ -81, +81 @@

    . {{{scp -p KEYS people.apache.org:/www/www.apache.org/dist/lucene/solr/}}}
   1. Start a new section in CHANGES.txt
   1. Wait 24 hours for release to propagate to mirrors. Check 
http://www.apache.org/dyn/closer.cgi/lucene/solr/
-  1. Add the new release info to the 
[[http://svn.apache.org/repos/asf/lucene/solr/trunk/site/doap.rdf|doap.rdf]] 
file, and double check for any other updates that should be made to the doap 
file as well if it hasn't been updated in a while. (Note: this file is used to 
power [[http://projects.apache.org/projects/solr.html|Solr's Listing]] on 
http://projects.apache.org/ as well as the 
[[http://projects.apache.org/feeds/rss.xml|Recent Apache Releases]] RSS feed)
+  1. Add the new release info to the 
[[http://svn.apache.org/repos/asf/lucene/dev/trunk/solr/site/doap.rdf|doap.rdf]]
 file, and double check for any other updates that should be made to the doap 
file as well if it hasn't been updated in a while. (Note: this file is used to 
power [[http://projects.apache.org/projects/solr.html|Solr's Listing]] on 
http://projects.apache.org/ as well as the 
[[http://projects.apache.org/feeds/rss.xml|Recent Apache Releases]] RSS feed)
   1. Deploy new Solr site: [[Website_Update_HOWTO]]
   1. Deploy new main Lucene site. (You will need to be a PMC member to do 
this: http://wiki.apache.org/lucene-java/TopLevelProject#Updating_the_Website)
   1. Update Javadoc in 
{{{people.apache.org:/www/lucene.apache.org/solr/docs/api}}}.

Reply via email to