...

This depends on how active the tree is at the time. (Currently, it is not active enough to warrant a branch).

svn cp  -m "Creating wave-0.3-release branch" \
            https://svn.apache.org/repos/asf/incubator/wave/trunk \
            https://svn.apache.org/repos/asf/incubator/wave/branches/wave-0.3-release

...

1. 'ant dist' works from the unpacked source archives
2. Jar manifests contain LICENSE and NOTICE
3. Jar manifests have the following properties:

   Code Block
   Specification-Vendor Specification-Title Specification-Version Implementation-Vendor Implementation-Title Implementation-Version

   TODO: Do we need Extension-Name, Implementation-Vendor-Id as well?

Make a Release Candidate

Bump version number

Adjust 'waveinabox.version' in build.properties. Do not include RC in the version number here.

Create CHANGES

This could be assembled from either JIRA, or directly from the Subversion logs.
(Currently JIRA is not organized/complete-enough to do this, so subversion logs should be used).
The best way to get a list of all the commits since the previous release is by:

cd {project-base}/tags
svn log --stop-on-copy wave-0.3
#The last reported revision is the revision used for the tag.
#(Theoretically only one listed being a tag directory)
cd ..
svn log -v -rNNNN:HEAD trunk > CHANGES

Using 'svn diff' may be worthwhile if the time between releases shrinks, or for some emergency (security) release, where there may have only been a few commits between releases.
NOTE: Do not use selecting by date in subversion. As this is not fully reliable in the ASF repository.

Create RELEASE-NOTES

TODO: decide on a format
Refer to the notes used in the previous release for the format of how to write them.
Break at 80 chars as is conventional.
Include:

• Description of the project
• Any major changes (otherwise see CHANGES)
• Any compatibility issues (and mention if none)
• Any upgrading procedures needed
• Make another note of the required Java version

  Tag the RC

  Code Block
  svn co https://svn.apache.org/repos/incubator/wave/trunk wave-0.3-RC1

  Make the RC

  Run

  Code Block
  ant release

  .
  TODO: sign?
  Upload the src+bin tar+zip somewhere so that it can be found.
  Either put in your space at https://people.ap.ache.org/~name/, or make a folder and host in https://dist.apache.org/repos/dist/dev/incubator/wave.

Vote for release

Send a vote mail for RC

Send a message with subject 'VOTE Release Wave 0.3 based on RC1' email to wave-dev@incubator.apache.org.

(Incubator only) Vote for RC

Whilst Wave is still an incubating project, send a VOTE email to general@incubator.apache.org to get PMC votes.
TODO: detail vote counting strategy

Publish

TODO