[Db-derby Wiki] Update of "ReleasePublication" by KristianWaagan

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The "ReleasePublication" page has been changed by KristianWaagan:
http://wiki.apache.org/db-derby/ReleasePublication?action=diff&rev1=22&rev2=23

  
    * tally vote & announce
    * put files on mirrors
-   * create doc directory (for new branches) and copy documention from the new release
+   * create doc directory (for new branches) and copy documentation from the new release
    * create web page for release
    * possibly remove old versions from the mirror directory 
-   * deploy to maven repository
+   * deploy to Maven repository
    * announce release
    * tag release and check in the jars (for upgrade testing)
    * update the News section of the web site
@@ -188, +188 @@

  
   1. Deploy to Maven repository.
  
-   The detailed instructions for deploying Maven 2 artifacts to the Maven repositories are located in the Derby source tree as `maven2/README.txt`.
+   The detailed instructions for deploying Maven artifacts to the Maven repositories are located in the Derby source tree as `maven2/README.txt`.
    Below is a brief overview of the process.
  
-   a. If you do not already have the latest Maven 2 distribution, [[http://maven.apache.org/download.html|download it]], unpack it, and put the bin directory into your path so that you can run Maven commands. You also need GnuPG and ssh/scp.
+   a. If you do not already have a recent Maven distribution, [[http://maven.apache.org/download.html|download it]], unpack it, and put the bin directory into your path so that you can run Maven commands. You also need GnuPG.
  
-    {i} As of this writing, the latest 2.x version of Maven was 2.2.1.
+    {i} As of this writing, the latest 2.x version of Maven was 2.2.1. The POMs have also been tested with Maven 3.0.4.
     
-   a. Make sure you can log into people at apache dot org without specifying a password. This means you have to configure SSH to use key-based authentication. Also make sure that SSH picks up your Apache user name (action is required if your local account name is different from you Apache account name).
- 
    a. Make sure you have your private GPG key and passphrase available. It is recommended to make the passphrase available to Maven by using an agent, but alternatively you can specify it on the command line.
  
    a. `cd` into Derby's `maven2` directory.
@@ -209, +207 @@

  
     {i} This does not build Derby using Maven, it works by copying the pre-built jars.
  
-    {i} If you do not want to enter your pgp credentials for each artifact, specify your credentials on the command like this: `mvn "-Dgpg.passphrase=$PASSPHRASE" clean install`, where $PASSPHRASE is your pgp passphrase.
+    {i} If you do not want to enter your pgp credentials for each artifact, and you haven't set up a password agent, specify your credentials on the command like this: `mvn "-Dgpg.passphrase=$PASSPHRASE" clean install`, where $PASSPHRASE is your pgp passphrase.
  
    a. Verify the jars installed into your local Maven repository (i.e. `~/.m2/repository/org/apache/derby`).
  
    a. Deploy the artifacts to the Apache staging repository: `mvn deploy`
  
-    {i} Again, if you do not want to enter your pgp credentials for each artifact, specify your credentials on the command like this: `mvn "-Dgpg.passphrase=$PASSPHRASE" -Dmy_login=$APACHE_USERNAME deploy`, where $PASSPHRASE is your pgp passphrase and $APACHE_USERNAME is the username you use to log onto people.apache.org.
+    {i} Again, if you do not want to enter your pgp credentials for each artifact, and you haven't set up a password agent, specify your credentials on the command like this: `mvn "-Dgpg.passphrase=$PASSPHRASE" deploy`, where $PASSPHRASE is your pgp passphrase.
- 
-   a. Verify the group ownership and permissions on the deployed artifacts. In general it is nice to grant write access to other members of the community, but not to the world!
  
    a. Revert local modifications in the `maven2` directory.
+ 
+   a. Log in to Nexus to close the temporary staging repository. Others can now test the Maven artifacts you have produced.
+ 
+   a. After a successful vote, log in to Nexus and release the temporary staging repository. If the vote doesn't pass, drop the temporary staging repository.
  
    a. After some time, verify that the artifacts have propagated to the Maven repositories. For 10.6, artifacts appeared within a day at http://repo1.maven.org/maven2/org/apache/derby/ . It took 6 days for the artifacts to appear on the external aggregator site ( http://mvnrepository.com/artifact/org.apache.derby ).