Page History

...

The general incubator release guide is available here: http://incubator.apache.org/guides/releasemanagement.html^{Image Removed}
but since we are out of incubation the docs are here: http://www.apache.org/dev/release^{Image Removed}
The apache central maven repo release guide is available here: http://www.apache.org/dev/publishing-maven-artifacts.html^{Image Removed}

The release process takes about one hour to perform, don't do this in a hurry as it is important to perform each step in the correct order!

...

• you have created your GPG keys. For more information, please refer to Making GPG Keys and http://www.apache.org/dev/release-signing.html .
• you have a GPG client installed and on your shell's path. See http://www.gnupg.org/^{Image Removed}.
• you have a Subversion 1.5+ client installed and on your shell's path. See http://subversion.tigris.org/^{Image Removed}.
• you have a Java 1.4.2 JDK installed and on your shell's path. See http://java.sun.com/j2se/1.4.2/download.html^{Image Removed}.
• you have set the environment variable MAVEN_OPTS=-Xmx512m
• you are using Maven 2.0.x or 2.2.1+, as Maven 2.1.x is known to produce wrong gpg pom signatures (see MGPG-14).

...

Download the latest JDK 6 http://www.oracle.com/technetwork/java/javase/downloads/jdk6-downloads-1637591.html^{Image Removed}

Create a mvn6 shell script and add it to your PATH. This script makes sure you use Java 6 to build the release.

...

Edit CHANGELOG.txt in you favorite editor and add the closed issues for this release. Info can be exported from jira.

Go to: https://issues.apache.org/jira/browse/EMPIREDB/^{Image Removed}
In the versions due section go to the version you want to release
Click on release notes
Configure release notes to text
Copy the notes to our CHANGELOG.txt

...

Make sure your code is up to date, builds, is available in your snapshot repository and has no local changes

>mvn6 clean install
...
>mvn6 clean release:clean
...
>mvn6 release:prepare -Papache-release
...
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "Apache Empire-db Parent"? (org.apache.empire-db:empire-db-parent) 2.0.5: : 
What is SCM release tag or label for "Apache Empire-db Parent"? (org.apache.empire-db:empire-db-parent) empire-db-parent-2.0.5: : apache-empire-db-2.0.5-rc3
What is the new development version for "Apache Empire-db Parent"? (org.apache.empire-db:empire-db-parent) 2.0.6-SNAPSHOT: : 
[INFO] Transforming 'Apache Empire-db Parent'...
[INFO] Updating empire-db to 2.0.5
...

...

Close the staging repository

Go to: https://repository.apache.org^{Image Removed} and log in
Follow the steps as described on http://maven.apache.org/developers/release/releasing.html^{Image Removed} (Close the staging repository)

...

TODO we might want to switch to https://dist.apache.org/repos/dist/dev/^{Image Removed}<TLP name>/
as explained here: http://www.apache.org/dev/release#upload-ci^{Image Removed}

>cd target/checkout/empire-db-dist (we want to have the same artifacts in the dist as in the repo)
>./checksums.sh
...
All Done. Files available in ./target

...

Initiate a vote

Docs here: http://www.apache.org/dev/release#approving-a-release^{Image Removed}

The vote mail should look like this:unmigrated-wiki-markup

To: dev@empire-db.apache.org
Subject: \ [VOTE\] Release Apache Empire-db 2.0.5 (rc3)

Hi,

We have just prepared a 2.0.5 release and we are now looking for approval of the PMC to publish the release.
More info on release requirements can be found here: http://www.apache.org/dev/release#approving-a-release^{Image Removed}

These are the major changes from our previous 2.0.4 release:

• xxx
• xxx

Changelog: http://svn.apache.org/viewvc/empire-db/tags/apache-empire-db-2.0.5-rc3/CHANGELOG.txt?view=co^{Image Removed}

Subversion tag: https://svn.apache.org/repos/asf/empire-db/tags/apache-empire-db-2.0.5-rc3^{Image Removed}

Maven staging repository: https://repository.apache.org/content/repositories/orgapacheempire-db-044/^{Image Removed}

Distribution files are located here http://people.apache.org/~francisdb/empire-db/^{Image Removed}

Rat report for the tag is available here: http://people.apache.org/~francisdb/empire-db/rat.txt^{Image Removed}

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

...

Log in to nexus as described above,

Go to: https://repository.apache.org^{Image Removed} and log in
Follow the steps as described on http://maven.apache.org/developers/release/releasing.html^{Image Removed}
(go to the staging section, right click on the staged release and select release)

Set up new release in JIRA / close old one

• Go to https://issues.apache.org/jira/browse/EMPIREDB^{Image Removed}
• Click on Administer Project /Administration
• Click on Manage versions
• Release current version
• Create new / edit versions if needed

Move the release files to the dist location

Docs here: http://www.apache.org/dev/release#upload-ci^{Image Removed}

1. svn checkout https://dist.apache.org/repos/dist/release/empire-db/^{Image Removed} empire-db-dist-release
2. Create a subdirectory with the version number (i.e. 2.0.5)
3. Copy all distribution files from your apache home directory to that directory (.zip, .tar.gz, .asc, .md5, .sha)
   scp francisdb@people.apache.org:~/public_html/empire-db/apache-empire-db-* .
4. commit to the subversion repo
5. Wait (one day) before files become available on the mirrors

...

1. Check out or update the Empire-db website source files from https://svn.apache.org/repos/asf/empire-db/site^{Image Removed}
2. Update the doap_Empire-db.rdf file, add new version
3. Edit Pages with html editor (I am using Microsoft Expression Web)
4. Open page downloads/latest.htm and copy section with previous release files to downloads/previous.htm.
5. In downloads/latest.htm replace all reference to old version number with new version number.
6. Update news.html
7. so a svn delete on javadocs/empire-db
8. commit
9. recreate the empire-db folder
10. fetch the new javadoc jar from http://repo1.maven.org/maven2/org/apache/empire-db/empire-db/x.x.x/empire-db-x.x.x-javadoc.jar^{Image Removed}
11. extract into the javadocs/empire-db folder
12. svn add the empire-db folder
13. Commit all changes to svn repo.
14. Wait some time for changes to become available on the mirrors.

...

Start the mail as follows:unmigrated-wiki-markup

Subject: \ [ANNOUNCE\] Apache Empire-db xxx released

The Apache Empire-db team is pleased to announce the release of Apache Empire-db version xxx.
Apache Empire-db is a lightweight data access and persistence component for relational databases based on JDBC. http://empire-db.apache.org/^{Image Removed}

Wiki Markup\[add description and list of changes\]

Changelog: http://svn.apache.org/viewvc/empire-db/tags/apache-empire-db-xxx/CHANGELOG.txt?view=co^{Image Removed}

Download: http://empire-db.apache.org/downloads/latest.htm^{Image Removed}

Thank you for your interest in Apache Empire-db!

The Apache Empire-db Team.

...