commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Commons Wiki] Update of "CreatingReleases" by SiegfriedGoeschl
Date Sat, 24 Oct 2009 20:56:53 GMT
Dear Wiki user,

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

The "CreatingReleases" page has been changed by SiegfriedGoeschl.
http://wiki.apache.org/commons/CreatingReleases?action=diff&rev1=37&rev2=38

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

   * it is uploaded to a key server
   * it is signed on a key signing party
   * it is found in the KEY file (see https://svn.apache.org/repos/asf/commons/trunks-proper)
-  
+ 
- See also: 
+ See also:
   * http://www.apache.org/dev/release-signing.html
   * http://www.gnupg.org/gph/en/manual.html
   * http://people.apache.org/~henkp/sig/pgp-key-signing.txt
  
  ==== A.3 Maven Installation ====
  
- Currently Maven 2.0.10 or better is required to run the release process 
-  
+ After having a lot of problems (Oct. 2009) the following configuration is known to work
+  * Maven 2.2.1
+  * SVN 1.5.0
+ 
  ==== A.4 Maven Server Settings ====
  
  It is a good idea to check your ''settings.xml'' that it contains the corresponding server
entries for the repositories and websites defined in the commons parent pom. If you have a
different user name on your box than on ''people.apache.org'' you local user name will be
used for authentication. Therefore the authentication will fail and after a few retries your
are locked out from ''people.apache.org'' for a day - which in turn makes cutting a release
rather lengthy. In theory you could also provide your password in the server section below
but this unsafe and did not work in my case.
@@ -46, +48 @@

      <id>apache.releases</id>
      <username>YOUR_APACHE_USERNAME</username>
      <filePermissions>664</filePermissions>
-     <directoryPermissions>775</directoryPermissions>    
+     <directoryPermissions>775</directoryPermissions>
    </server>
    <server>
      <id>apache.website</id>
      <username>YOUR_APACHE_USERNAME</username>
      <filePermissions>664</filePermissions>
-     <directoryPermissions>775</directoryPermissions>    
+     <directoryPermissions>775</directoryPermissions>
    </server>
    <server>
      <id>apache.snapshots</id>
      <username>YOUR_APACHE_USERNAME</username>
      <filePermissions>664</filePermissions>
-     <directoryPermissions>775</directoryPermissions>    
+     <directoryPermissions>775</directoryPermissions>
    </server>
- </servers>  
+ </servers>
  }}}
  
  === B. Release Preparation ===
@@ -105, +107 @@

  The commons-build plugin generates a download page in {{{./src/site/xdoc/}}} based on {{{commons.release.version}}}
  
  {{{
- mvn commons:download-page 
+ mvn commons:download-page
  }}}
  
  ==== B.3 Define Staging Site for Release Candidate ====
@@ -141, +143 @@

  
  Check that your poms will not lose content when they are rewritten during the release process.
  
-  * mvn release:prepare -!DdryRun=true 
+  * mvn release:prepare -!DdryRun=true
  
   * Diff the original file pom.xml with the one called pom.xml.tag to see if the license
or any other info has been removed. '''This has been known to happen if the starting <project>
tag is not on a single line.''' The only things that should be different between these files
are the <version> and <scm> elements. Any other changes, you must backport yourself
to the original pom.xml file and commit before proceeding with the release.
  
@@ -156, +158 @@

   1. {{{mvn -Prc release:perform}}}
  
  ==== C.2 Remove SHA1 and MD5 Fingerprints of PGP Signatures ====
-  
+ 
  During the release process some unwanted fingerprints of all ASCII-armored files are generated,
e.g. "commons-foo.jar.asc.md5" and "commons-foo.jar.asc.sha1". It is a good idea to remove
them manually for the time being.
  
  === D. Vote ===
@@ -207, +209 @@

  
  ==== E.2 Copy Artifacts from Staging ====
  
- The Maven Stage plugin copies the artifacts (from your release candidate) to the M2 sync
directory (people.apache.org/repo/m2-ibiblio-rsync-repository). 
+ The Maven Stage plugin copies the artifacts (from your release candidate) to the M2 sync
directory (people.apache.org/repo/m2-ibiblio-rsync-repository).
  
  The following example was used to do the copy the artifacts for commonse-exec-1.0 based
on RC5
  
  {{{
  mvn stage:copy -Dsource="http://people.apache.org/builds/commons/exec/1.0/RC5/staged/" \
    -Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository"
\
-   -DtargetRepositoryId=apache.releases \ 
+   -DtargetRepositoryId=apache.releases \
    -Dversion=1.0
  }}}
-  
+ 
  ==== E.3 Deploy the Site ====
  
  Run {{{mvn site-deploy}}} to deploy the site - please note that you are deploying the site
of the next development snapshot.
+ 
+ ==== E.4 Create the SVN Release Tag ====
+ 
+ If you have used a "RC" tag (e.g. "EXEC_1_0_1_RC5") for the M2 release preparation you need
to copy the SVN tag in order to create an official release tag.
+ 
+ The following example was used for creating the release tag on commons-exec-1.0.1
+ 
+ {{{
+ svn copy https://svn.apache.org/repos/asf/commons/proper/exec/tags/EXEC_1_0_1_RC5 \
+   https://svn.apache.org/repos/asf/commons/proper/exec/tags/EXEC_1_0_1 \
+   -m "The RC5 passed to vote so this will be the release tag"
+ }}}
  
  === F. Celebrate ===
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message