Page History

...

• You have setup your own public OpenGPG key signature for signing the distribution
• You can login to Nexus
• You have a Git workspace for clone of https://git-wip-us.apache.org/repos/asf/tapestry-5.git (Tapestry source code project)
• You have a Subversion workspace for Subversion checkout of https://dist.apache.org/repos/dist/dev/tapestry (dev archives workspaceartifact archive)
• You have a Subversion workspace for checkout of https://dist.apache.org/repos/dist/release/tapestry (release archives workspaceartifact archive)
• You have a Subversion workspace for checkout of https://svn.apache.org/repos/infra/websites/production/tapestry/content (site content workspace)

GIT and Deployment Credentials

...

You can find your keyId using gpg --list-keys.

 The apacheArchivesFolder should be  You should set apacheArchivesFolder to the full path to of your dev archives workspacelocal dev artifact archives directory (see above). The build will copy files to this folder; see further notes below.

Release Steps

1. Generate the Release

1. Update your workspace to In your Tapestry source code project directory, switch to the release branch
   1. For current work, the release branch is master
   2. When creating bug fix releases for older releases, the branch will match the release, e.g., 5.3
2. Run the build using gradle generateRelease
   
   1. This will create, sign, and upload JAR files and other artifacts to the Nexus repository
   2. It will also create, sign, and copy the source, binary, and documentation archives to your dev archives workspace dev artifact archive directory
3. Tag the release in Git, then push the changes up to the Apache repository:
   1. git tag 5.x
   2. git push --tags
4. Login to Nexus and close the automatically created staging repository

...

1. The build will have copied archive files to your dist workspace dev artifact archive directory.
2. svn add the new files
3. svn commit to copy the files up to Apache (this is slow)
   1. Use the full version number as the commit message, e.g., 5.4-beta-26
4. You can verify the files via the web: https://dist.apache.org/repos/dist/dev/tapestry

...

1. Use the Manage Versions page in JIRA to add a new version (this is often not necessary as it is often created by someone earlier)if not already created).
2. Release the version, moving outstanding issues to the next version.
3. Generate HTML Release Notes
   1. Visit the TAP5 Versions pages in JIRA
   2. Choose the correct version number
   3. Click "Release Notes" (upper right corner of the page)
   4. Create a new Confluence child page of Release Process Notes (it may already exist)
   5. Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
   6. Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
   7. Rename the "Bug" heading to "Bugs Fixed", "Improvement" to "Improvements Made", "New Feature" to "New Features Added"
   8. Update Release Process index Notes index page to point to the new page

...

1. Copy the release archives files (including checksums and GPG signatures) to the your release artifact archives workspace directory
2. Change to the release archives workspace
3. svn add and and svn commit, as with the dev archives workspace

...

1. Update the release number listed in the following pages in the Confluence wiki:
   
   Release Process
   1. Download page
   2. (Optional) Tutorial Release Process Tutorial Creating The Skeleton Application page: Tapestry version number in the archetype
   3. (Optional) Release Process  Getting Started page: Tapestry version number in the archetype
2. Change Switch to the site content workspaceSVN project.
3. svn update to get any recent changes.
4. Edit  archetype-catalog.xml to add or update a new entry for the release
5. Update Edit the doap.rdf file with the release number and date inside doap.rdf  (this is a description file for the project).
6. svn commit

11. Blog & Tweet

...