[CONF] Apache Felix: Release Management (page created)

[confluence]

Page Created : FELIX : Release Management Release Management has been created by Carsten Ziegeler (Mar 12, 2008). Content: This is a draft for a how to about releasing artifacts from Apache Felix: Most of the work is done by Maven. Prerequisites Each and every release must be signed; therefore the public key should be cross signed by other Apache committers (not required but suggested). The public key should be added to http://www.apache.org/dist/felix/KEYS Building the Release Candidates Make sure that an appropriate version for the release is entered in Jira Build the release artifacts with Maven (the following instructions work on Unix systems, for Windows use a different path than /tmp) mvn -Prelease -Darguments="-Prelease -DaltDeploymentRepository=local::default::file:///tmp" -DaltDeploymentRepository=local::default::file:///tmp release:prepare mvn -Prelease -Darguments="-Prelease -DaltDeploymentRepository=local::default::file:///tmp" -DaltDeploymentRepository=local::default::file:///tmp release:perform The above commands created a tag in svn, deployed the release candidates into your /tmp directory, signed the binaries and created the md5/sha1 files. Upload these files to people.apache.org into your home folder and put them there together with the KEYS file containing your public key so we can verify the signatures. Start the vote thread, wait 72 hours. If the vote fails (easy case first) remove the tag from svn - done If the vote is successful, copy the released artifacts to the dist directory on www.apache.org, delete the old release there (its archived), and deploy the release to the maven repository. Create a new version for the artifact in jira.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences