[CONF] Apache Tapestry > Release Process

[confluence]

Release Process Page edited by Howard M. Lewis Ship Changes (1) ... # Once files reach all mirrors, update the Downloads Page Note the first step; the Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory. A template for the vote e-mail: ... Full Content The process can be summarized as: Update your Subversion workspace mvn release:prepare mvn release:perform Generate and upload Binary / Source distributions Login to Nexus, 'close' automatically created staging repository and note its url. Send vote email ... 3 days pass Login to Nexus and promote the release SSH to people.apache.org and copy the Binary / Source distributions to the right diretory Once files reach all mirrors, update the Downloads Page Note the first step; the Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory. 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 binary 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.X tag in Subversion: http://svn.apache.org/viewvc/tapestry/tapestry5/tags/releases/5.X.X/ On a successful vote, I'll move the files from these directories to the proper distribution directories and update the Tapestry site documentation. Vote will run for three days; on success I'll move the voted artifacts into place and send out appropriate notifications. I often embellish this template with extra detail. Change Notification Preferences View Online | View Changes