Release ProcessPage edited by Howard M. Lewis Ship
Comment:
Add note about relinking the current symlink
Changes (16)
Full ContentPrerequisitesBefore creating a release ensure:
SVN and Deployment CredentialsTo successfully create a release, you will need to update your Maven Settings with the credentials for your SVN user and the deployment user. These credentials are stored in the Gradle configuration file ~/.gradle/gradle.properties: apacheDeployUserName=hlship apacheDeployPassword=... signing.keyId=7CC19136 signing.secretKeyRingFile=/Users/hlship/.gnupg/secring.gpg signing.password=...
A template for the vote e-mail:I've created and uploaded a release of Tapestry 5.x.x, ready to be voted upon. The source and source downloads are uploaded to: http://people.apache.org/~XXX/tapestry-releases/ and the Maven artifacts staged to: https://repository.apache.org/content/repositories/orgapachetapestry-XXX/ Please examine these files to determine if the new release, 5.x.x, is ready. I've also created a 5.X tag in Subversion: http://svn.apache.org/viewvc/tapestry/tapestry5/tags/releases/5.x.x/ Vote will run for three days; On a successful vote, I'll release the Maven artifacts, and move the source and javadoc distributions from these directories to the proper distribution directories and update the Tapestry site documentation, and send out appropriate notifications. I often embellish this template with extra detail.
Change Notification Preferences
View Online
|
View Changes
|
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence
- [CONF] Apache Tapestry > Release Process confluence