Versions Compared

Old Version 21

changes.mady.by.user Richard S. Hall

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (mcculls)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  1. remove the release tag from Subversion (svn del ...)
  2. login to https://repository.apache.org using your Apache SVN credentials. Click on Staging on the left. Then click on org.apache.felix in the list of repositories. In the panel below you should see a closed repository that is linked to your username and IP (if it's not yet closed you need to right click and select Close). Right click on this repository and select Drop.
  3. rollback the version in the pom.xml and commit any fixes you need to make
Info

The release manager is free to either reuse the same version when proposing a new release for vote (for example 2.1.2 after a failed 2.1.2 release attempt), or choose a different number (for example 2.1.4 after a failed 2.1.2 attempt). (cf. vote on 02/14/11).

Promoting the Release

If the vote passes:

  1. copy the released artifacts to the Felix dist directory (/x1/www/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 select it, and choose Promote. Select the Releases repository from the drop-down list and click Promoteclick the Release button.
  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 at news
  7. update the download page on the website at downloads to point to the new release.

...

Appendix A: create and add your key to http://www.apache.org/dist/felix/KEYSImage Removed

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 Removed 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/KEYSImage Removed you must wait 2 hours

...