Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Create the distribution

Wiki Markup
\[TODO\] make sure the release.sh script does not delete existing files?

Code Block
>cd target/checkout/empire-db-dist (we want to have the same artifacts in the dist as in the repo)
>./releasechecksums.sh
...
Distribution build completedAll Done. Files available in ./target/dist

OR (if the previous failed/is not possible any more)

this might not work, not tested, probably creates new artifacts instead of using existing ones

Code Block
>svn checkout https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-empire-db-2.0.5-incubating-rc3
...
>cd apache-empire-db-2.0.5-incubating-rc3/empire-db-dist/
>mvn5 clean install -Papache-release
>./releasechecksums.sh
...
Distribution build completedAll Done. Files available in target/dist

The script will first ask your GPG passphrase and then generate the distribution and the rat report.
You might see this. This is buggy reporting from the rat plugin so just ignore. Check the rat report manually at target/dist/rat.txt

Code Block

[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Too many unapproved licenses: 317
./target

Now upload the generated files + rat report to your apache personal directory.

Code Block
>cd target/dist
>scp * people.apache.org:~/public_html/empire-db

Now remove the .pom on the remote machine

Initiate a vote

As we are currently in the incubator we need two voting rounds. Fist we need a non-binding community vote on the dev@ list. After that we need a IPMC / Mentor vote on general@. It's also a good idea to point our mentors to that vote by ding a post on private@.

...