[CONF] Apache Wicket: Releasing (page edited)

Mon, 04 May 2009 09:27:34 -0700

Page Edited : WICKET : Releasing

Releasing has been edited by Igor Vaynberg (May 04, 2009).

(View changes)

Content:

Releasing Apache Wicket 1.4.x

Building the release

  1. query dev@ for any open issues, it helps to look at JIRA first
  2. create tag, create release branch
  3. check out release branch
  4. Set correct version in the pom files:
    • Linux:
      • find . -name "pom.xml" | xargs sed -i -e "s/1.4-SNAPSHOT/1.4-m1/g"
      • find . -name "pom.xml" | xargs sed -i -e "s/wicket\/trunk/wicket\/releases\/wicket-1.4-m1/g"
    • Mac OS X:
      • find . -name "pom.xml" | xargs sed -i "" -e "s/1.4-SNAPSHOT/1.4-m1/g"
      • find . -name "pom.xml" | xargs sed -i "" -e "s/wicket\/trunk/wicket\/releases\/wicket-1.4-m1/g"
  5. add JIRA generated release notes to CHANGELOG-1.4
  6. commit to release branch
  7. call release.sh
  8. test the distribution (examples, rat, etc)
  9. upload m2-repo and dist directory from target/ to p.a.o (see below)
  10. upload commons/KEY into dist folder on p.a.o
  11. send vote message
  12. wait
  13. upload to mirrors (see below)
  14. release the version in JIRA
  15. wait 24 hours for mirrors to pick them up
  16. announce

Releasing Apache Wicket 1.3.x

Building the release

  1. query dev@ for any open issues, it helps to look at JIRA first
  2. create tag, create release branch
  3. check out release branch
  4. Set correct version in the pom files:
    • Linux:
      • find . -name "pom.xml" | xargs sed -i -e "s/1.3-SNAPSHOT/1.3.2/g"
      • find . -name "pom.xml" | xargs sed -i -e "s/wicket\/trunk/wicket\/releases\/wicket-1.3.3/g"
    • Mac OS X:
      • find . -name "pom.xml" | xargs sed -i "" -e "s/1.3-SNAPSHOT/1.3.2/g"
      • find . -name "pom.xml" | xargs sed -i "" -e "s/wicket\/trunk/wicket\/releases\/wicket-1.3.3/g"
  5. add JIRA generated release notes to CHANGELOG-1.3
  6. commit to release branch
  7. call release.sh
  8. test the distribution (examples, rat, etc)
  9. upload m2-repo and dist directory from target/ to p.a.o
  10. upload commons/KEY into dist folder on p.a.o
  11. send vote message
  12. wait
  13. upload to mirrors (see below)
  14. release the version in JIRA
  15. wait 24 hours for mirrors to pick them up
  16. announce

Uploading to the mirror system

http://apache.org/dev/mirror-step-by-step.html

Uploading to maven repository

I haven't got any really good way to put them in the maven mirrors. The problem is that right now we override the meta xml files, so only the latest version is listed. If we really should do this perfect we would modify meta files like /org/apache/wicket/wicket/maven-metadata.xml and add the version to it (as well as create the hashes again).

But for now this is sufficient:

  1. cd into the directory you have the artifacts which has been voted on.
  2. cp -R m2-repo/org/apache/wicket/* /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/wicket/
  3. chmod -R g+w * /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/wicket

Further reading: README under /www/people.apache.org/repo/m2-ibiblio-rsync-repository/

Announce

  1. http://wicket.apache.org
    1. http://wicket.apache.org/getting-wicket.html
  2. u...@wicket.apache.org,d...@wicket.apache.org,annou...@apache.org
  3. Misc. websites like javalobby, serverside, onjava etc.

Additional tasks

  1. add the release to http://wicket.apache.org/quickstart.html and set it as default
  2. upload the JavaDocs to the website at http://wicket.apache.org/docs/wicket-x.y.z/ and point JavaDocs link to it

Releasing Apache Wicket 1.2.x

TBD...

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

Unsubscribe or edit your notifications preferences

Reply via email to