Page History

...

Canceling the Release

Promoting the Release

If the vote is successful:

1. copy the released artifacts to the Felix dist directory (/www.apache.org/dist/felix) on people.apache.org
2. delete the old release from the Felix dist directory (it's archived)
3. login to https://repository.apache.org with your Apache SVN credentials. Click on Staging. Find your closed staging repository, right click on it and choose Promote. Select the Releases repository from the drop-down list and click Promote.
4. next click on Repositories, select the Releases repository and validate that your artifacts are all there
5. if you're releasing bundles, you can also add them to the Felix Release OBR (see Appendix C).
6. update the news section on the website
7. update the download page on the website to point to the new release.

For the last two tasks, it's better to give the mirrors some time to distribute the uploaded artifacts (one day should be fine). This ensures that once the website (news and download page) is updated, people can actually download the artifacts.

Appendix A: create and add your key to http://www.apache.org/dist/felix/KEYS^{Image Added}

If you are using a *nix system with a working OpenSSH, GnuPG, and bash you can create and add your own key with the following command:

1. Create a public/private pair key:

   Code Block
   gpg --gen-key

   When gpg asks for e-mail linked the key you MUST USE the <committer>@apache.org one
   When gpg asks for comment linked the key you SHOULD USE "CODE SIGNING KEY"
2. Add the key to http://www.apache.org/dist/felix/KEYS:^{Image Added} type the following command replacing the word e-mail with your Apache's one (<committer>@apache.org).

   Code Block
   (gpg --list-sigs e-mail && gpg --export --armor e-mail) > toadd.key scp toadd.key people.apache.org: ssh people.apache.org "cat toadd.key >> /x1/www/www.apache.org/dist/felix/KEYS"

3. You are now DONE, but to see the changes on http://www.apache.org/dist/felix/KEYS^{Image Added} you must wait 2 hours

Appendix B: preparing releases on Mac OS X

...

This is due to a bug in Subversion on the Mac, as described by Brett Porter in his blog. He proposes putting an "svn" script at the head of your path to fix the issue.

Appendix

...

C: deploying bundles to the Felix OBR

If you're releasing bundles, you can also add them to the Felix Release OBR. To do this, execute the following command:

...