[CONF] Apache Tapestry Release Process

2014-09-02 Thread Howard M. Lewis Ship (Confluence)














  


Howard M. Lewis Ship edited the page:
 


Release Process   






...
To 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:



 Code Block




 

apacheDeployUserName=hlship
apacheDeployPassword=...

signing.keyId=7CC19136
signing.secretKeyRingFile=/Users/hlship/.gnupg/secring.gpg
signing.password=...
 



...
A template for the vote e-mail:



 No Format




 

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/~USER/tapestry-releases/

and the Maven artifacts staged to:

https://repository.apache.org/content/repositories/orgapachetapestry-xxx/staging

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 Git:

https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=c5600a8de7645fb7bd5cc21b38f8902a36c1b840

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.
 



...






 View Online   Like   View Changes  
 Stop watching space   Manage Notifications  


 


 


  This message was sent by Atlassian Confluence 5.0.3, Team Collaboration Software  






[CONF] Apache Tapestry Release Process

2013-04-29 Thread confluence







Release Process
Page edited by Massimo Lusetti


Comment:
update to reflect changes on our site managements, please check and correct if something is wrong


 Changes (2)
 




...
** Create (if necessary) {{/www/tapestry.apache.org/5.x.x}} to store documentation for the release ** Unpack the JavaDoc archive into the directory (it will become the {{apidocs}} directory) 
** Relink {{/www/tapestry.apache.org/current/}} to point to the new {{5.x.x}} directory 
** Update SVN PubSub repo at https://svn.apache.org/repos/infra/websites/production/tapestry/content/ to clean old api dir and relink all symlinks to point to the new {{5.x.x}} directory 
* Once files reach all mirrors, update the Downloads Page * Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page) 
...


Full Content

Prerequisites 

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Bible





 Page:
 Version Numbers





 Page:
 Release Process





 Page:
 Developer Information





 Page:
 Building Tapestry from Source






Before creating a release ensure:


	You have setup your own public OpenGPG key signature for signing the distribution
	You can login to Nexus
	Your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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=...



Release Steps

The process can be summarized as:


	Update your workspace to the release branch, currently 5.3:  git co 5.3
	
		It is normal for the release branch to be created a week or more before the planned release
	
	
	Update build.gradle to set the version number, then git commit
	
		Don't forget to set it back to 5.x-SNAPSHOT after the release
	
	
	Run the build using gradle generateRelease
	
		This will create, sign, and upload JAR files and other artifacts to the Nexus repository
		It will also create, sign, and upload the source and javadoc archives to your ~/public_html/tapestry-releases folder of your Apache home directory (at people.apache.org)
	
	
	Tag the release in Git, then push the changes up to the Apache repository:
	
		git tag 5.x.x
		git push --tags
	
	
	Update build.gradle to bump the version number to 5.x(.y)?-SNAPSHOT, then git commit
	Login to Nexus and close the automatically created staging repository, and note its url
	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)
	Release the version, moving outstanding issues to the next version
	Generate HTML Release Notes
	
		Visit the TAP5 Versions pages in JIRA
		Choose the correct version number
		Click "Release Notes" (upper right corner of the page)
		Create a new Confluence child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Rename the "Bug" heading to "Bugs Fixed", "Improvement" to "Improvements Made", "New Feature" to "New Features Added"
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Apache Tapestry 5.x.x" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
		Releasing will ultimately get the artifacts up 

[CONF] Apache Tapestry Release Process

2013-02-11 Thread confluence







Release Process
Page edited by Bob Harner


Comment:
Added reminder to update the DOAP file with latest release number


 Changes (1)
 




...
** (Optional) Tutorial [Creating The Skeleton Application] page: Tapestry version number in the archetype ** (Optional) [Getting Started] page: Tapestry version number in the archetype 
* Update the release number and date at http://svn.apache.org/repos/asf/tapestry/tapestry-site/branches/post-5.2-site/publish/doap_Tapestry.rdf  
h2. A template for the vote e-mail:  
...


Full Content

Prerequisites 

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Release Process





 Page:
 Developer Information





 Page:
 Developer Bible





 Page:
 Building Tapestry from Source





 Page:
 Version Numbers






Before creating a release ensure:


	You have setup your own public OpenGPG key signature for signing the distribution
	You can login to Nexus
	Your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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=...



Release Steps

The process can be summarized as:


	Update your workspace to the release branch, currently 5.3:  git co 5.3
	
		It is normal for the release branch to be created a week or more before the planned release
	
	
	Update build.gradle to set the version number, then git commit
	
		Don't forget to set it back to 5.x-SNAPSHOT after the release
	
	
	Run the build using gradle generateRelease
	
		This will create, sign, and upload JAR files and other artifacts to the Nexus repository
		It will also create, sign, and upload the source and javadoc archives to your ~/public_html/tapestry-releases folder of your Apache home directory (at people.apache.org)
	
	
	Tag the release in Git, then push the changes up to the Apache repository:
	
		git tag 5.x.x
		git push --tags
	
	
	Update build.gradle to bump the version number to 5.x(.y)?-SNAPSHOT, then git commit
	Login to Nexus and close the automatically created staging repository, and note its url
	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)
	Release the version, moving outstanding issues to the next version
	Generate HTML Release Notes
	
		Visit the TAP5 Versions pages in JIRA
		Choose the correct version number
		Click "Release Notes" (upper right corner of the page)
		Create a new Confluence child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Rename the "Bug" heading to "Bugs Fixed", "Improvement" to "Improvements Made", "New Feature" to "New Features Added"
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Apache Tapestry 5.x.x" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
		Releasing will ultimately get the artifacts up to the central Maven repository
	
	
	Documentation and Downloads:
	
		SSH to people.apache.org and move the source and javadoc archives to /www/www.apache.org/dist/tapestry/
		Create (if necessary) /www/tapestry.apache.org/5.x.x to store documentation for the release
		Unpack the JavaDoc archive into the directory (it will 

[CONF] Apache Tapestry Release Process

2012-11-06 Thread confluence







Release Process
Page edited by Bob Harner


Comment:
Added a step for tweaking the Release Notes headings


 Changes (1)
 




...
** Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes) ** Paste the HTML release notes content into the new page (youll have to use the \{html\} macro) 
** Rename the Bug heading to Bugs Fixed, Improvement to Improvements Made, New Feature to New Features Added 
** Update [Release Notes] index page to point to the new page * Send vote email ... *3 days pass* 
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Bible





 Page:
 Developer Information





 Page:
 Release Process






Before creating a release ensure:


	You have setup your own public OpenGPG key signature for signing the distribution
	You can login to Nexus
	Your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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=...



Release Steps

The process can be summarized as:


	Update your workspace to the release branch, currently 5.3:  git co 5.3
	
		It is normal for the release branch to be created a week or more before the planned release
	
	
	Update build.gradle to set the version number, then git commit
	
		Don't forget to set it back to 5.x-SNAPSHOT after the release
	
	
	Run the build using gradle generateRelease
	
		This will create, sign, and upload JAR files and other artifacts to the Nexus repository
		It will also create, sign, and upload the source and javadoc archives to your ~/public_html/tapestry-releases folder of your Apache home directory (at people.apache.org)
	
	
	Tag the release in Git, then push the changes up to the Apache repository:
	
		git tag 5.x.x
		git push --tags
	
	
	Update build.gradle to bump the version number to 5.x(.y)?-SNAPSHOT, then git commit
	Login to Nexus and close the automatically created staging repository, and note its url
	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)
	Release the version, moving outstanding issues to the next version
	Generate HTML Release Notes
	
		Visit the TAP5 Versions pages in JIRA
		Choose the correct version number
		Click "Release Notes" (upper right corner of the page)
		Create a new Confluence child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Rename the "Bug" heading to "Bugs Fixed", "Improvement" to "Improvements Made", "New Feature" to "New Features Added"
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Apache Tapestry 5.x.x" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
		Releasing will ultimately get the artifacts up to the central Maven repository
	
	
	Documentation and Downloads:
	
		SSH to people.apache.org and move the source and javadoc archives to /www/www.apache.org/dist/tapestry/
		Create (if necessary) /www/tapestry.apache.org/5.x.x to store documentation for the release
		Unpack the JavaDoc archive into the directory (it will become the apidocs directory)
		Relink /www/tapestry.apache.org/current/ to point to the new 5.x.x directory
	
	
	Once files reach all mirrors, update the Downloads Page
	Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page)
	Edit 

[CONF] Apache Tapestry Release Process

2012-11-02 Thread confluence







Release Process
Page edited by Bob Harner


Comment:
Reduced the number of places that need to be updated with a new release.


 Changes (3)
 




...
* Update the release number listed in the following pages in the Confluence wiki: ** [Documentation] page: Current stable release number 
** Tutorial [Creating The Skeleton Application] page: Tapestry version number in the archetype ** [Getting Started] page: Tapestry version number in the archetype ** [downloadBoxes] page (part of the home page): Tapestry version number 
** [TAPESTRY:Download] page 
 
** (Optional) Tutorial [Creating The Skeleton Application] page: Tapestry version number in the archetype ** (Optional) [Getting Started] page: Tapestry version number in the archetype 
h2. A template for the vote e-mail:  
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Bible





 Page:
 Developer Information





 Page:
 Release Process






Before creating a release ensure:


	You have setup your own public OpenGPG key signature for signing the distribution
	You can login to Nexus
	Your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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=...



Release Steps

The process can be summarized as:


	Update your workspace to the release branch, currently 5.3:  git co 5.3
	
		It is normal for the release branch to be created a week or more before the planned release
	
	
	Update build.gradle to set the version number, then git commit
	
		Don't forget to set it back to 5.x-SNAPSHOT after the release
	
	
	Run the build using gradle generateRelease
	
		This will create, sign, and upload JAR files and other artifacts to the Nexus repository
		It will also create, sign, and upload the source and javadoc archives to your ~/public_html/tapestry-releases folder of your Apache home directory (at people.apache.org)
	
	
	Tag the release in Git, then push the changes up to the Apache repository:
	
		git tag 5.x.x
		git push --tags
	
	
	Update build.gradle to bump the version number to 5.x(.y)?-SNAPSHOT, then git commit
	Login to Nexus and close the automatically created staging repository, and note its url
	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)
	Release the version, moving outstanding issues to the next version
	Generate HTML Release Notes
	
		Visit the TAP5 Versions pages in JIRA
		Choose the correct version number
		Click "Release Notes" (upper right corner of the page)
		Create a new Confluence child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Apache Tapestry 5.x.x" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
		Releasing will ultimately get the artifacts up to the central Maven repository
	
	
	Documentation and Downloads:
	
		SSH to people.apache.org and move the source and javadoc archives to /www/www.apache.org/dist/tapestry/
		Create (if necessary) /www/tapestry.apache.org/5.x.x to store documentation for the release
		Unpack the JavaDoc archive into the directory (it will become the apidocs directory)
		Relink /www/tapestry.apache.org/current/ to point to the new 5.x.x directory
	
	
	Once files reach all mirrors, update the Downloads Page
	Create a 

[CONF] Apache Tapestry Release Process

2012-11-02 Thread confluence







Release Process
Page edited by Bob Harner


Comment:
Further reduced the number of places that need to be updated with a new release.


 Changes (1)
 




...
* Edit {{/www/tapestry.apache.org/archetype-catalog.xml}} to add or update a new entry for the release * Update the release number listed in the following pages in the Confluence wiki: 
** [Documentation] page: Current stable release number 
** [TAPESTRY:Download] page ** (Optional) Tutorial [Creating The Skeleton Application] page: Tapestry version number in the archetype 
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Bible





 Page:
 Developer Information





 Page:
 Release Process






Before creating a release ensure:


	You have setup your own public OpenGPG key signature for signing the distribution
	You can login to Nexus
	Your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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=...



Release Steps

The process can be summarized as:


	Update your workspace to the release branch, currently 5.3:  git co 5.3
	
		It is normal for the release branch to be created a week or more before the planned release
	
	
	Update build.gradle to set the version number, then git commit
	
		Don't forget to set it back to 5.x-SNAPSHOT after the release
	
	
	Run the build using gradle generateRelease
	
		This will create, sign, and upload JAR files and other artifacts to the Nexus repository
		It will also create, sign, and upload the source and javadoc archives to your ~/public_html/tapestry-releases folder of your Apache home directory (at people.apache.org)
	
	
	Tag the release in Git, then push the changes up to the Apache repository:
	
		git tag 5.x.x
		git push --tags
	
	
	Update build.gradle to bump the version number to 5.x(.y)?-SNAPSHOT, then git commit
	Login to Nexus and close the automatically created staging repository, and note its url
	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)
	Release the version, moving outstanding issues to the next version
	Generate HTML Release Notes
	
		Visit the TAP5 Versions pages in JIRA
		Choose the correct version number
		Click "Release Notes" (upper right corner of the page)
		Create a new Confluence child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Apache Tapestry 5.x.x" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
		Releasing will ultimately get the artifacts up to the central Maven repository
	
	
	Documentation and Downloads:
	
		SSH to people.apache.org and move the source and javadoc archives to /www/www.apache.org/dist/tapestry/
		Create (if necessary) /www/tapestry.apache.org/5.x.x to store documentation for the release
		Unpack the JavaDoc archive into the directory (it will become the apidocs directory)
		Relink /www/tapestry.apache.org/current/ to point to the new 5.x.x directory
	
	
	Once files reach all mirrors, update the Downloads Page
	Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page)
	Edit /www/tapestry.apache.org/archetype-catalog.xml to add or update a new entry for the release
	Update the release number listed in the following pages in the Confluence 

[CONF] Apache Tapestry Release Process

2012-08-20 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (21)
 




...
The process can be summarized as:  
* Update your _Subversion_ workspace to the release branch {{[https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x]}} 
* Update your workspace to the release branch, currently 5.3:  {{git co 5.3}} 
** It is normal for the release branch to be created a week or more before the planned release 
* Tag the release in Subversion {{svn copy https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/5.x}} 
* Update {{build.gradle}} to set the version number, then {{git commit}} 
* Run the build using {{gradle generateRelease}} ** This will create, sign, and upload JAR files and other artifacts to the Nexus repository ** It will also create, sign, and upload the source and javadoc archives to your {{~/public_html/tapestry-releases}} folder of your Apache home directory (at people.apache.org) 
* Tag the release in Git, then push the changes up to the Apache repository:** {{git tag 5.x.x}}   ** {{git push --tags}} 
* Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *close* the automatically created staging repository, and note its url * Use the [Manage Versions page|https://issues.apache.org/jira/plugins/servlet/project-config/TAP5/versions] in JIRA to add a new version (this is often not necessary as it is often created by someone earlier) 
...
* Send vote email ... *3 days pass* * Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *release* the versions repository 
** Enter Apache Tapestry 5.x.x (adjust as necessary) for the message 
** The version will disappear from the list of repositories after releasing it ** Releasing will ultimately get the artifacts up to the central Maven repository * Documentation and Downloads: ** SSH to people.apache.org and move the source and javadoc archives to {{/www/www.apache.org/dist/tapestry/}} 
** Create (if necessary) {{/www/tapestry.apache.org/5.x.x}} to store documentation for the release 
** Unpack the JavaDoc archive into the directory (it will become the {{apidocs}} directory) 
** Relink {{/www/tapestry.apache.org/current/}} to point to the new {{5.x.x}} directory 
* Once files reach all mirrors, update the Downloads Page * Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page) 
...
 {noformat} 
Ive created and uploaded a release of Tapestry 5.x.x, ready to be voted upon. 
voted upon. 
 The source and source downloads are uploaded to:  
http://people.apache.org/~XXX/tapestry-releases/ http://people.apache.org/~USER/tapestry-releases/ 
 and the Maven artifacts staged to:  
https://repository.apache.org/content/repositories/orgapachetapestry-XXX/ https://repository.apache.org/content/repositories/orgapachetapestry-xxx/ 
 
Please examine these files to determine if the new release, 5.x.x, is ready. 
 
Ive also created a 5.X 5.x.x tag in Subversion: Git: 
 
http://svn.apache.org/viewvc/tapestry/tapestry5/tags/releases/5.x/ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=c5600a8de7645fb7bd5cc21b38f8902a36c1b840 
 
Vote will run for three days; On a successful vote, Ill release the Maven artifacts, 
artifacts, and move the source and javadoc distributions from these directories to the proper distribution 
to the proper distribution directories and update the Tapestry site 
directories and update the Tapestry site documentation, and send out appropriate notifications. 
 
{noformat}  I often embellish this template with extra detail. 
 Lately, I append a text version of the JIRA release notes as well. 


Full Content

Prerequisites

Related Articles


 Page:
 Developer Information





 Page:
 Release Process





 Page:
 Confluence Site Setup

   

[CONF] Apache Tapestry Release Process

2012-02-23 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


Comment:
Add note about relinking the current symlink


 Changes (16)
 




...
** Sign with your key (as specified above) the source and javadoc archives then copy them to {{~/public_html/tapestry-releases}} folder of your Apache home directory (at people.apache.org) * Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *close* the automatically created staging repository, and note its url 
* Use the [Manage Versions page|https://issues.apache.org/jira/plugins/servlet/project-config/TAP5/versions] in JIRA to add a new version (this is often not necessary as it is often created by someone earlier) 
* *Release* the version, moving outstanding issues to the new next version 
* Generate HTML Release Notes ** Visit the [TAP5 Versions pages in JIRA|https://issues.apache.org/jira/browse/TAP5#selectedTab=com.atlassian.jira.plugin.system.project:versions-panelsubset=-1] 
...
* Send vote email ... *3 days pass* * Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *release* the versions repository 
** Enter Apache Tapestry 5.x.x (adjust as necessary) for the message 
** The version will disappear from the list of repositories after releasing it 
* Documentation and Downloads: 
* ** SSH to people.apache.org and move the source and javadoc archives to {{/www/www.apache.org/dist/tapestry/}} 
** Create (if necessary) {{/www/tapestry.apache.org/5.x.x}} to store documentation for the release ** Unpack the JavaDoc archive into the directory (it will become the {{apidocs}} directory) ** Relink {{/www/tapestry.apache.org/current/}} to point to the new {{5.x.x}} directory 
* Once files reach all mirrors, update the Downloads Page * Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page) 
* Create (if necessary) {{//www/tapestry.apache.org/5.x}} to store documentation for the release * Unpack the JavaDoc archive into the directory (it will become the {{apidocs}} directory) 
* Edit {{/www/tapestry.apache.org/archetype-catalog.xml}} to add or update a new entry for the release * Update the release number listed in the following pages in the Confluence wiki: 
...
 {noformat} 
Ive created and uploaded a release of Tapestry 5.x.x, ready to be 
voted upon.  
...
https://repository.apache.org/content/repositories/orgapachetapestry-XXX/  
Please examine these files to determine if the new release, 5.X, 5.x.x, is ready. 
 Ive also created a 5.X tag in Subversion:  
http://svn.apache.org/viewvc/tapestry/tapestry5/tags/releases/5.X/ http://svn.apache.org/viewvc/tapestry/tapestry5/tags/releases/5.x.x/ 
 
On a successful vote, Ill release the Maven artifaces, and move the source and javadoc 
Vote will run for three days; On a successful vote, Ill 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. 
directories and update the Tapestry site documentation, and send out appropriate notifications. 
 
Vote will run for three days; on success Ill move the voted artifacts into place and send out appropriate notifications.  
{noformat}  
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Information





 Page:
 Developer Bible





 Page:
 Release Process






Before creating a release ensure:


	you have setup your own public OpenGPG key signature for signing the distribution
	you can login to Nexus
	your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To successfully create a release, you will need to update your 

[CONF] Apache Tapestry Release Process

2012-02-23 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


Comment:
The build now signs and uploads the source/javadoc archives


 Changes (8)
 




...
Before creating a release ensure:  
* yYou have setup your own public OpenGPG key signature for signing the distribution 
* yYou can login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] 
* yYour local _settings.xml_ contains valid SVN and deployment credentials 
  
...
The process can be summarized as:  
* Update your _Subversion_ workspace to the release branch {{[https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x.x]}} 
** It is normal for the release branch to be created a week or more before the planned release 
* Tag the release in Subversion {{svn copy https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x.x https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/5.x.x}} 
* Run the build using {{gradle generateRelease}} 
** This will create, sign, and upload JAR files and other artifacts to the Nexus repository 
** It will also create, but not upload, the source and javadoc archives ** Sign with your key (as specified above) the source and javadoc archives then copy them to {{~/public_html/tapestry-releases}} folder of your Apache home directory (at people.apache.org) 
** It will also create, sign, and upload the source and javadoc archives to your {{~/public_html/tapestry-releases}} folder of your Apache home directory (at people.apache.org) 
* Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *close* the automatically created staging repository, and note its url * Use the [Manage Versions page|https://issues.apache.org/jira/plugins/servlet/project-config/TAP5/versions] in JIRA to add a new version (this is often not necessary as it is often created by someone earlier) 
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Information





 Page:
 Developer Bible





 Page:
 Release Process






Before creating a release ensure:


	You have setup your own public OpenGPG key signature for signing the distribution
	You can login to Nexus
	Your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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=...



Release Steps

The process can be summarized as:


	Update your Subversion workspace to the release branch https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x.x
	
		It is normal for the release branch to be created a week or more before the planned release
	
	
	Tag the release in Subversion svn copy https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x.x https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/5.x.x
	Run the build using gradle generateRelease
	
		This will create, sign, and upload JAR files and other artifacts to the Nexus repository
		It will also create, sign, and upload the source and javadoc archives to your ~/public_html/tapestry-releases folder of your Apache home directory (at people.apache.org)
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	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)
	Release the version, moving outstanding issues to the next version
	Generate HTML Release Notes
	
		Visit the TAP5 Versions pages in JIRA
		Choose the correct version number
		Click "Release Notes" (upper right corner of the page)
		Create a new Confluence child page of Release Notes (it may already exist)
		Update 

[CONF] Apache Tapestry Release Process

2011-12-21 Thread confluence







Release Process
Page edited by Massimo Lusetti


 Changes (2)
 




...
** This will upload JAR files to the Nexus repository ** It will also create, but not upload, the source and javadoc archives 
** Copy the source and javadoc archives to {{~/tapestry-releases}} folder of your Apache home directory (at people.apache.org) 
** Sign with your key (as specified above) the source and javadoc archives then copy them to {{~/public_html/tapestry-releases}} folder of your Apache home directory (at people.apache.org) 
* Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *close* the automatically created staging repository, and note its url * Use the [Manage Versions page|https://issues.apache.org/jira/plugins/servlet/project-config/TAP5/versions] in JIRA to add a new version (this is often not necessary) 
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Information





 Page:
 Developer Bible





 Page:
 Release Process






Before creating a release ensure:


	you have setup your own public OpenGPG key signature for signing the distribution
	you can login to Nexus
	your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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=...



Release Steps

The process can be summarized as:


	Update your Subversion workspace to the release branch https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x
	
		It is normal for the release branch to be created a week or more before the planned release
	
	
	Tag the release in Subversion svn copy https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/5.x
	Run the build using gradle generateRelease
	
		This will upload JAR files to the Nexus repository
		It will also create, but not upload, the source and javadoc archives
		Sign with your key (as specified above) the source and javadoc archives then copy them to ~/public_html/tapestry-releases folder of your Apache home directory (at people.apache.org)
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new version (this is often not necessary)
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes
	
		Visit the TAP5 Versions pages in JIRA
		Choose the correct version number
		Click "Release Notes" (upper right corner of the page)
		Create a new Confluence child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Apache Tapestry 5.x" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
	
	
	SSH to people.apache.org and move the source and javadoc archives to /www/www.apache.org/dist/tapestry/
	Once files reach all mirrors, update the Downloads Page
	Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page)
	Create (if necessary) //www/tapestry.apache.org/5.x to store documentation for the release
	Unpack the JavaDoc archive into the directory (it will become the apidocs directory)
	Edit /www/tapestry.apache.org/archetype-catalog.xml to add or update a new entry for the release
	Update the release number listed in the following pages in the Confluence wiki:
	
		Documentation page: 

[CONF] Apache Tapestry Release Process

2011-11-14 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


Comment:
Attempt to update this for current Gradle build, etc.


 Changes (26)
 




...
h2. SVN and Deployment Credentials  
To 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 Maven Settings Gradle configuration file in _\~/.m2/settings.xml_. {{~/.gradle/gradle.properties}}: 
{code}settings 
 
... {code} 
apacheDeployUserName=hlship apacheDeployPassword=... 
 
servers signing.keyId=7CC19136 
server signing.secretKeyRingFile=/Users/hlship/.gnupg/secring.gpg 
idsvn.apache.org/id signing.password=... 
 usernameyouruser/username  passwordsecretpassword/password   /serverserver  idapache.releases.https/id  usernameyouruser/username  passwordsecretpassword/password   /server/servers ...  /settings{code}  h2. Maintenance Releases  A maintenance release is created from a maintenance branch. If you are creating a maintenance release, ensure that the scm settings refer to the branch and not to trunk, as shown in the following example.  {code}  scm connectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//developerConnection urlhttp://svn.apache.org/viewvc/tapestry/tapestry5/branches/maint-5-2//url   /scm 
{code}  
h2. Release Steps  The process can be summarized as:  
* Update your _Subversion_ workspace to {{[https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk]}} the release branch {{[https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x]}} 
* Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off -SNAPSHOT) * Commit that change to SVN * First do a dry run {{mvn release:prepare \-DautoVersionSubmodules=true \-DdryRun=true}} in order to check that modifications to poms and scm operations (only listed on the console) are working as expected. To clean up the dry release preparation perform {{mvn release:clean}}  * {{mvn release:prepare \-DautoVersionSubmodules=true}} * {{mvn release:perform}} * Generate and upload Binary / Source distributions ** {{svn sw}} {{[https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/]}}{_}version_ ** The {{ant}} build script creates the distributions ** Theres some manual work to sign and upload the distributions 
** It is normal for the release branch to be created a week or more before the planned release * Tag the release in Subversion {{svn copy https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/5.x}} * Run the build using {{gradle generateRelease}} ** This will upload JAR files to the Nexus repository ** It will also create, but not upload, the source and javadoc archives ** Copy the source and javadoc archives to {{~/tapestry-releases}} folder of your Apache home directory (at people.apache.org) 
* Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *close* the automatically created staging repository, and note its url 
* Use the [Manage Versions page|https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310833] in JIRA to add a new version (this is often not necessary) 
* *Release* the version, moving outstanding issues to the new version * Generate [HTML Release Notes|https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310833] for the version 
...
* Send vote email ... *3 days pass* * Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *release* the versions repository 
** Enter Apache Tapestry 5.x.x beta release (adjust as necessary) for the message 
** The version will disappear from the list of repositories after releasing it 
* SSH to people.apache.org and copy the Binary / Source distributions to the right directory 
* SSH to people.apache.org and move the source and javadoc archives to {{/www/www.apache.org/dist/tapestry/}} 
* Once files reach all mirrors, update the Downloads Page * Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page) 
* Generate and deploy site documentation: ** {{mvn  

[CONF] Apache Tapestry Release Process

2011-11-14 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


Comment:
Ah, yes, the Maven archetype


 Changes (1)
 




...
* Create (if necessary) {{//www/tapestry.apache.org/5.x}} to store documentation for the release * Unpack the JavaDoc archive into the directory (it will become the {{apidocs}} directory) 
* Edit {{//www/tapestry.apache.org/archetype-catalog.xml}} to add or update a new entry for the release 
* Update the release number listed in the following pages in the Confluence wiki: ** [Documentation] page: Current stable release number 
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Information





 Page:
 Developer Bible





 Page:
 Release Process






Before creating a release ensure:


	you have setup your own public OpenGPG key signature for signing the distribution
	you can login to Nexus
	your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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=...



Release Steps

The process can be summarized as:


	Update your Subversion workspace to the release branch https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x
	
		It is normal for the release branch to be created a week or more before the planned release
	
	
	Tag the release in Subversion svn copy https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/5.x https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/5.x
	Run the build using gradle generateRelease
	
		This will upload JAR files to the Nexus repository
		It will also create, but not upload, the source and javadoc archives
		Copy the source and javadoc archives to ~/tapestry-releases folder of your Apache home directory (at people.apache.org)
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new version (this is often not necessary)
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes for the version
	
		Create a new child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Apache Tapestry 5.x" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
	
	
	SSH to people.apache.org and move the source and javadoc archives to /www/www.apache.org/dist/tapestry/
	Once files reach all mirrors, update the Downloads Page
	Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page)
	Create (if necessary) //www/tapestry.apache.org/5.x to store documentation for the release
	Unpack the JavaDoc archive into the directory (it will become the apidocs directory)
	Edit //www/tapestry.apache.org/archetype-catalog.xml to add or update a new entry for the release
	Update the release number listed in the following pages in the Confluence wiki:
	
		Documentation page: "Current stable release" number
		Tutorial Creating The Skeleton Application page: Tapestry version number in the archetype
		Getting Started page: Tapestry version number in the archetype
		downloadBoxes page (part of the home page): Tapestry version number
	
	



A template for the vote e-mail:



I've created and uploaded a release of Tapestry 5.x, ready to be
voted upon.

The source and source downloads are uploaded to:


[CONF] Apache Tapestry Release Process

2011-07-02 Thread confluence







Release Process
Page edited by Bob Harner


Comment:
Reducing the number of places to have to update the version number in the docs


 Changes (2)
 




...
* Update the release number listed in the following pages in the Confluence wiki: ** [Documentation] page: Current stable release number 
** Tutorial [Dependencies, Tools and Plugins] page: Tapestry version number at the bottom 
** Tutorial [Creating The Skeleton Application] page: Tapestry version number in the archetype (3 places) 
** [Getting Started] page: Tapestry version number in the archetype ** [downloadBoxes] page (part of the home page): Tapestry version number 
...


Full Content

Prerequisites

Related Articles


 Page:
 Developer Bible





 Page:
 Release Process





 Page:
 Confluence Site Setup





 Page:
 Developer Information






Before creating a release ensure:


	you have setup your own public OpenGPG key signature for signing the distribution
	you can login to Nexus
	your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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 Maven Settings file in /.m2/settings.xml.

settings

   ...

   servers
  server
 idsvn.apache.org/id
 usernameyouruser/username
 passwordsecretpassword/password
  /server

  server
 idapache.releases.https/id
 usernameyouruser/username
 passwordsecretpassword/password
  /server
   /servers

   ...

/settings


Maintenance Releases

A maintenance release is created from a maintenance branch. If you are creating a maintenance release, ensure that the scm settings refer to the branch and not to trunk, as shown in the following example.


  scm
connectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//connection
developerConnectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//developerConnection
urlhttp://svn.apache.org/viewvc/tapestry/tapestry5/branches/maint-5-2//url
  /scm




Release Steps

The process can be summarized as:


	Update your Subversion workspace to https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off "-SNAPSHOT")
	Commit that change to SVN
	First do a "dry run" mvn release:prepare DautoVersionSubmodules=true DdryRun=true in order to check that modifications to poms and scm operations (only listed on the console) are working as expected. To clean up the dry release preparation perform mvn release:clean
	mvn release:prepare DautoVersionSubmodules=true
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		svn sw https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/version
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new version
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes for the version
	
		Create a new child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Tapestry 5.x.x beta release" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
	
	
	SSH to people.apache.org and copy the Binary / Source distributions to the right 

[CONF] Apache Tapestry Release Process

2011-05-04 Thread confluence







Release Process
Page edited by Bob Harner


Comment:
Added 4 more wiki pages to edit for updating version number


 Changes (1)
 




...
** {{mvn  clean site site:deploy \-Pjavadoc}} ** Budget about _30 minutes_ for this to run\! 
* Update the release number listed in the following pages in the Confluence wiki: ** [Documentation] page: Current stable release number ** Tutorial [Dependencies, Tools and Plugins] page: Tapestry version number at the bottom ** Tutorial [Creating The Skeleton Application] page: Tapestry version number in the archetype (3 places) ** [Getting Started] page: Tapestry version number in the archetype 
 
{warning} Be aware that Maven will perform some automatic Subversion commits, and even create the new release tag for you\! Make 
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Bible





 Page:
 Developer Information





 Page:
 Release Process






Before creating a release ensure:


	you have setup your own public OpenGPG key signature for signing the distribution
	you can login to Nexus
	your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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 Maven Settings file in /.m2/settings.xml.

settings

   ...

   servers
  server
 idsvn.apache.org/id
 usernameyouruser/username
 passwordsecretpassword/password
  /server

  server
 idapache.releases.https/id
 usernameyouruser/username
 passwordsecretpassword/password
  /server
   /servers

   ...

/settings


Maintenance Releases

A maintenance release is created from a maintenance branch. If you are creating a maintenance release, ensure that the scm settings refer to the branch and not to trunk, as shown in the following example.


  scm
connectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//connection
developerConnectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//developerConnection
urlhttp://svn.apache.org/viewvc/tapestry/tapestry5/branches/maint-5-2//url
  /scm




Release Steps

The process can be summarized as:


	Update your Subversion workspace to https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off "-SNAPSHOT")
	Commit that change to SVN
	First do a "dry run" mvn release:prepare DautoVersionSubmodules=true DdryRun=true in order to check that modifications to poms and scm operations (only listed on the console) are working as expected. To clean up the dry release preparation perform mvn release:clean
	mvn release:prepare DautoVersionSubmodules=true
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		svn sw https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/version
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new version
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes for the version
	
		Create a new child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Tapestry 5.x.x beta release" (adjust as necessary) for the message
		The version will disappear from the 

[CONF] Apache Tapestry Release Process

2011-03-23 Thread confluence







Release Process
Page edited by Igor Drobiazko


 Changes (11)
 




h2. Prerequisites  Before creating a release ensure:  * you have setup your own public OpenGPG key signature for signing the distribution * you can login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] * your local _settings.xml_ contains valid SVN and deployment credentials   h2. SVN and Deployment Credentials  To 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 Maven Settings file in _\~/.m2/settings.xml_. {code}settings ... servers   server  idsvn.apache.org/id  usernameyouruser/username  passwordsecretpassword/password   /serverserver  idapache.releases.https/id  usernameyouruser/username  passwordsecretpassword/password   /server/servers ...  /settings{code}  
h2. Release Steps  {float:right|background="" {contentbylabel:title=Related Articles|showLabels=false|showSpace=false|labels=tapestry-dev} 
{float} 
 
The process can be summarized as:  
* Update your _Subversion_ workspace to {{[https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk]}} 
* Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off -SNAPSHOT) * Commit that change to SVN 
* {{mvn release:prepare \-DautoVersionSubmodules=true}} 
* {{mvn release:perform}} * Generate and upload Binary / Source distributions 
** {{svn sw https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/}}_version_ 
** {{svn sw}} {{[https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/]}}{_}version_ 
** The {{ant}} build script creates the distributions ** Theres some manual work to sign and upload the distributions 
...
** Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes) ** Paste the HTML release notes content into the new page (youll have to use the \{html\} macro) 
** Update [Release Notes] index page to point to the new page 
* Send vote email ... *3 days pass* * Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *release* the versions repository 
...
* Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page) * Generate and deploy site documentation: 
** {{mvn  clean site site:deploy \-Pjavadoc}} 
** Budget about _30 minutes_ for this to run\! 
  {warning} 
Be aware that Maven will perform some automatic Subversion commits, and even create the new release tag for you\! Make 
sure to get those version numbers right; Ive found to my dismay that it can be tricky to correct this after-the-fact. {warning} 
...
 rm -rf /www/www.apache.org/dist/tapestry/tapestry-*5.2.1*  mv * /www/www.apache.org/dist/tapestry/ 
 
{code}  
...
h2. Notes  
{{mvn release:prepare}} does a very good job at guessing the right version numbers (i.e., stripping off the \-SNAPSHOT suffix for the release version, 
and incrementing the version number for the new development version). If its one of your first releases, consider trying {{mvn release:prepare \-DdryRun=true}} and manually observing the differences in the poms (this command will not commit the updated poms - itll just generate them). See [the Maven documentation|http://maven.apache.org/plugins/maven-release-plugin/introduction.html] for more details. 
 The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory. 
...
{noformat} Ive created and uploaded a release of Tapestry 5.x.x, ready to be 
voted upon. 
 The binary and source downloads are uploaded to: 
...


Full Content

Prerequisites

Before creating a release ensure:


	you have setup your own public OpenGPG key signature for signing the distribution
	you can login to Nexus
	your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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 

[CONF] Apache Tapestry Release Process

2011-03-23 Thread confluence







Release Process
Page edited by Igor Drobiazko


 Changes (1)
 




...
/settings{code}  
h2. Maintenance Releases  A maintenance release is created from a maintenance branch. If you are creating a maintenance release, ensure that the scm settings refer to the branch and not to trunk, as shown in the following example.  {code}  scm connectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//developerConnection urlhttp://svn.apache.org/viewvc/tapestry/tapestry5/branches/maint-5-2//url   /scm {code}   
h2. Release Steps  
...


Full Content

Prerequisites

Before creating a release ensure:


	you have setup your own public OpenGPG key signature for signing the distribution
	you can login to Nexus
	your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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 Maven Settings file in /.m2/settings.xml.

settings

   ...

   servers
  server
 idsvn.apache.org/id
 usernameyouruser/username
 passwordsecretpassword/password
  /server

  server
 idapache.releases.https/id
 usernameyouruser/username
 passwordsecretpassword/password
  /server
   /servers

   ...

/settings


Maintenance Releases

A maintenance release is created from a maintenance branch. If you are creating a maintenance release, ensure that the scm settings refer to the branch and not to trunk, as shown in the following example.


  scm
connectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//connection
developerConnectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//developerConnection
urlhttp://svn.apache.org/viewvc/tapestry/tapestry5/branches/maint-5-2//url
  /scm




Release Steps


Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Bible





 Page:
 Developer Information





 Page:
 Release Process





The process can be summarized as:


	Update your Subversion workspace to https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off "-SNAPSHOT")
	Commit that change to SVN
	mvn release:prepare DautoVersionSubmodules=true
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		svn sw https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/version
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new version
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes for the version
	
		Create a new child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Tapestry 5.x.x beta release" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
	
	
	SSH to people.apache.org and copy the Binary / Source distributions to the right directory
	Once files reach all mirrors, update the Downloads Page
	Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page)
	Generate and deploy site documentation:
	
		mvn  clean site site:deploy Pjavadoc
		

[CONF] Apache Tapestry Release Process

2011-03-23 Thread confluence







Release Process
Page edited by Igor Drobiazko


 Changes (3)
 




h2. Prerequisites 
{float:right|background="" {contentbylabel:title=Related Articles|showLabels=false|showSpace=false|labels=tapestry-dev} {float} 
 Before creating a release ensure: 
...
h2. Release Steps  
{float:right|background="" {contentbylabel:title=Related Articles|showLabels=false|showSpace=false|labels=tapestry-dev} {float} 
The process can be summarized as:  
...
* Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off -SNAPSHOT) * Commit that change to SVN 
* First do a dry run {{mvn release:prepare \-DautoVersionSubmodules=true \-DdryRun=true}} in order to check that modifications to poms and scm operations (only listed on the console) are working as expected. To clean up the dry release preparation perform {{mvn release:clean}}  
* {{mvn release:prepare \-DautoVersionSubmodules=true}} * {{mvn release:perform}} 
...


Full Content

Prerequisites

Related Articles


 Page:
 Confluence Site Setup





 Page:
 Developer Bible





 Page:
 Developer Information





 Page:
 Release Process






Before creating a release ensure:


	you have setup your own public OpenGPG key signature for signing the distribution
	you can login to Nexus
	your local settings.xml contains valid SVN and deployment credentials




SVN and Deployment Credentials

To 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 Maven Settings file in /.m2/settings.xml.

settings

   ...

   servers
  server
 idsvn.apache.org/id
 usernameyouruser/username
 passwordsecretpassword/password
  /server

  server
 idapache.releases.https/id
 usernameyouruser/username
 passwordsecretpassword/password
  /server
   /servers

   ...

/settings


Maintenance Releases

A maintenance release is created from a maintenance branch. If you are creating a maintenance release, ensure that the scm settings refer to the branch and not to trunk, as shown in the following example.


  scm
connectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//connection
developerConnectionscm:svn:https://svn.apache.org/repos/asf/tapestry/tapestry5/branches/maint-5-2//developerConnection
urlhttp://svn.apache.org/viewvc/tapestry/tapestry5/branches/maint-5-2//url
  /scm




Release Steps

The process can be summarized as:


	Update your Subversion workspace to https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off "-SNAPSHOT")
	Commit that change to SVN
	First do a "dry run" mvn release:prepare DautoVersionSubmodules=true DdryRun=true in order to check that modifications to poms and scm operations (only listed on the console) are working as expected. To clean up the dry release preparation perform mvn release:clean
	mvn release:prepare DautoVersionSubmodules=true
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		svn sw https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/version
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new version
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes for the version
	
		Create a new child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML 

[CONF] Apache Tapestry Release Process

2010-11-19 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
* Generate and deploy site documentation: ** {{mvn  clean site site:deploy -Pjavadoc}} 
** Budget about _30 minutes_ for this to run! 
  
...

Full Content

Release Steps

The process can be summarized as:


	Update your Subversion workspace to https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off "-SNAPSHOT")
	Commit that change to SVN
	mvn release:prepare -DautoVersionSubmodules=true
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		svn sw https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/version
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new version
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes for the version
	
		Create a new child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Tapestry 5.x.x beta release" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
	
	
	SSH to people.apache.org and copy the Binary / Source distributions to the right directory
	Once files reach all mirrors, update the Downloads Page
	Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page)
	Generate and deploy site documentation:
	
		mvn  clean site site:deploy -Pjavadoc
		Budget about 30 minutes for this to run!
	
	




Be aware that Maven will perform some automatic Subversion commits, and even create the new release tag for you! Make
sure to get those version numbers right; I've found to my dismay that it can be tricky to correct this after-the-fact.

There's a couple of steps to moving the distributions; you have to delete the prior release (unless its a stable release) and get some permissions set up correctly:



 cd public_html/tapestry-releases/
 ls -l
total 43631
-rw-r--r--  1 hlship  tapestry  8722101 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2.md5
-rw-r--r--  1 hlship  tapestry  8750103 Oct 24 15:58 tapestry-bin-5.2.2.tar.gz
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:58 tapestry-bin-5.2.2.tar.gz.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:58 tapestry-bin-5.2.2.tar.gz.md5
-rw-r--r--  1 hlship  tapestry  8823868 Oct 24 15:58 tapestry-bin-5.2.2.zip
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:58 tapestry-bin-5.2.2.zip.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:58 tapestry-bin-5.2.2.zip.md5
-rw-r--r--  1 hlship  tapestry  4920211 Oct 24 15:59 tapestry-src-5.2.2.tar.bz2
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:59 tapestry-src-5.2.2.tar.bz2.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:59 tapestry-src-5.2.2.tar.bz2.md5
-rw-r--r--  1 hlship  tapestry  5409252 Oct 24 15:59 tapestry-src-5.2.2.tar.gz
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:59 tapestry-src-5.2.2.tar.gz.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:59 tapestry-src-5.2.2.tar.gz.md5
-rw-r--r--  1 hlship  tapestry  7618776 Oct 24 16:00 tapestry-src-5.2.2.zip
-rw-r--r--  1 hlship  tapestry  195 Oct 24 16:00 tapestry-src-5.2.2.zip.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 16:00 tapestry-src-5.2.2.zip.md5
 chmod 664 *
 rm -rf /www/www.apache.org/dist/tapestry/tapestry-*5.2.1*
 mv * /www/www.apache.org/dist/tapestry/
 





Notes

mvn release:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version). If it's one of your first releases, consider trying mvn release:prepare -DdryRun=true and manually observing the differences in the poms (this command will not commit the updated poms - it'll just generate them). See the Maven documentation for more details.

The Maven code assumes it is executing inside 

[CONF] Apache Tapestry Release Process

2010-11-12 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
* Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *close* the automatically created staging repository, and note its url * Use the [Manage Versions page|https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310833] in JIRA to add a new release (the new development release) 
* *Release* the version, moving outstanding issues to the new version 
* Generate [HTML Release Notes|https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310833] for the release ** Create a new child page of [Release Notes] (it may already exist) 
...

Full Content

Release Steps

The process can be summarized as:


	Update your Subversion workspace
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number to be released
	mvn release:prepare
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new release (the new development release)
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes for the release
	
		Create a new child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the release
	
		Enter "Tapestry 5.x.x beta release" (adjust as necessary) for the message
		The release will disappear from the list of repositories after releasing it
	
	
	SSH to people.apache.org and copy the Binary / Source distributions to the right directory
	Once files reach all mirrors, update the Downloads Page
	Create a Confluence blog entry to describe the new release (this will automatically appear on the home page)




Be aware that Maven will perform some automatic Subversion commits, and even create the new release tag for you! Make
sure to get those version numbers right; I've found to my dismay that it can be tricky to correct this after-the-fact.

There's a couple of steps to moving the distributions; you have to delete the prior release (unless its a stable release) and get some permissions set up correctly:



 cd public_html/tapestry-releases/
 ls -l
total 43631
-rw-r--r--  1 hlship  tapestry  8722101 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2.md5
-rw-r--r--  1 hlship  tapestry  8750103 Oct 24 15:58 tapestry-bin-5.2.2.tar.gz
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:58 tapestry-bin-5.2.2.tar.gz.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:58 tapestry-bin-5.2.2.tar.gz.md5
-rw-r--r--  1 hlship  tapestry  8823868 Oct 24 15:58 tapestry-bin-5.2.2.zip
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:58 tapestry-bin-5.2.2.zip.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:58 tapestry-bin-5.2.2.zip.md5
-rw-r--r--  1 hlship  tapestry  4920211 Oct 24 15:59 tapestry-src-5.2.2.tar.bz2
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:59 tapestry-src-5.2.2.tar.bz2.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:59 tapestry-src-5.2.2.tar.bz2.md5
-rw-r--r--  1 hlship  tapestry  5409252 Oct 24 15:59 tapestry-src-5.2.2.tar.gz
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:59 tapestry-src-5.2.2.tar.gz.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:59 tapestry-src-5.2.2.tar.gz.md5
-rw-r--r--  1 hlship  tapestry  7618776 Oct 24 16:00 tapestry-src-5.2.2.zip
-rw-r--r--  1 hlship  tapestry  195 Oct 24 16:00 tapestry-src-5.2.2.zip.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 16:00 tapestry-src-5.2.2.zip.md5
 chmod 664 *
 rm -rf /www/www.apache.org/dist/tapestry/tapestry-*5.2.1*
 mv * /www/www.apache.org/dist/tapestry/
 





Notes

mvn release:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version). If it's one of your first releases, consider trying mvn release:prepare -DdryRun=true and manually observing the differences in the poms (this command will not commit the updated poms - it'll just 

[CONF] Apache Tapestry Release Process

2010-11-12 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (8)
 



...
 * Update your _Subversion_ workspace 
* Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off -SNAPSHOT) 
* mvn release:prepare * mvn release:perform 
* {{mvn release:prepare}} * {{mvn release:perform}} 
* Generate and upload Binary / Source distributions ** {{svn sw https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/}}_version_ 
...
** Theres some manual work to sign and upload the distributions * Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *close* the automatically created staging repository, and note its url 
* Use the [Manage Versions page|https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310833] in JIRA to add a new release (the new development release) version 
* *Release* the version, moving outstanding issues to the new version 
* Generate [HTML Release Notes|https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310833] for the release version 
** Create a new child page of [Release Notes] (it may already exist) ** Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes) 
...
** Update [Release Notes] index page to point to the new page  * Send vote email ... *3 days pass* 
* Login to [Nexus|https://repository.apache.org/index.html#stagingRepositories] and *release* the release versions repository 
** Enter Tapestry 5.x.x beta release (adjust as necessary) for the message 
** The release version will disappear from the list of repositories after releasing it 
* SSH to people.apache.org and copy the Binary / Source distributions to the right directory * Once files reach all mirrors, update the Downloads Page 
* Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page) 
  
...

Full Content

Release Steps

The process can be summarized as:


	Update your Subversion workspace
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number about to be released (i.e., strip off "-SNAPSHOT")
	mvn release:prepare
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		svn sw https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/version
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus and close the automatically created staging repository, and note its url
	Use the Manage Versions page in JIRA to add a new version
	Release the version, moving outstanding issues to the new version
	Generate HTML Release Notes for the version
	
		Create a new child page of Release Notes (it may already exist)
		Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)
		Paste the HTML release notes content into the new page (you'll have to use the {html} macro)
		Update Release Notes index page to point to the new page
	
	
	Send vote email ... 3 days pass
	Login to Nexus and release the version's repository
	
		Enter "Tapestry 5.x.x beta release" (adjust as necessary) for the message
		The version will disappear from the list of repositories after releasing it
	
	
	SSH to people.apache.org and copy the Binary / Source distributions to the right directory
	Once files reach all mirrors, update the Downloads Page
	Create a Confluence blog entry to describe the new release (this will automatically appear on the Tapestry home page)




Be aware that Maven will perform some automatic Subversion commits, and even create the new release tag for you! Make
sure to get those version numbers right; I've found to my dismay that it can be tricky to correct this after-the-fact.

There's a couple of steps to moving the distributions; you have to delete the prior release (unless its a stable release) and get some permissions set up correctly:



 cd public_html/tapestry-releases/
 ls -l
total 43631
-rw-r--r--  1 hlship  tapestry  8722101 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2
-rw-r--r--  1 hlship  tapestry  195 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2.asc
-rw-r--r--  1 hlship  tapestry   33 Oct 24 15:58 tapestry-bin-5.2.2.tar.bz2.md5
-rw-r--r--  1 hlship  tapestry  8750103 Oct 24 15:58 tapestry-bin-5.2.2.tar.gz

[CONF] Apache Tapestry Release Process

2010-10-24 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
 * Update your _Subversion_ workspace 
* Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/*) quickstart/src/main/resources/archetype-resources/pom.xml) to the version number to be released 
* mvn release:prepare * mvn release:perform 
...

Full Content

Release Steps

The process can be summarized as:


	Update your Subversion workspace
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/pom.xml) to the version number to be released
	mvn release:prepare
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus, 'close' the automatically created staging repository and note its url
	Use the Manage Versions page in JIRA to add a new release (the new development release)
	Generate HTML Release Notes for the release
	
		Create a new child page of Release Notes
		Paste the HTML content into the new page (you'll have to use the {html} macro)
		Update Release Notes to point to the new page
	
	
	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 directory
	Once files reach all mirrors, update the Downloads Page
	
		Dont forget to change the version number to the new release
		Dont forget to link to the new release's Release Notes page
	
	




Be aware that Maven will perform some automatic Subversion commits, and even create the new release tag for you! Make
sure to get those version numbers right; I've found to my dismay that it can be tricky to correct this after-the-fact.

Notes

mvn release:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version). If it's one of your first releases, consider trying mvn release:prepare -DdryRun=true and manually observing the differences in the poms (this command will not commit the updated poms - it'll just generate them). See the Maven documentation for more details.

The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory.

The correct response to this prompt:

What is the SCM release tag or label for "Tapestry 5 Project"

is

5.X.X

This reflects that Tapestry stores its SVN tags in a slightly weird way (that made perfect sense at the time).

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









[CONF] Apache Tapestry Release Process

2010-09-30 Thread confluence







Release Process
Page edited by Andreas Andreou


 Changes (3)
 



...
 * Update your _Subversion_ workspace 
* Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/*) to the version number to be released 
* mvn release:prepare * mvn release:perform 
...
h2. Notes  
{{mvn release:prepare}} does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version, 
and incrementing the version number for the new development version). If its one of your first releases, consider trying {{mvn release:prepare -DdryRun=true}} and manually observing the differences in the poms (this command will not commit the updated poms - itll just generate them). See [the Maven documentation|http://maven.apache.org/plugins/maven-release-plugin/introduction.html] for more details. 
 The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory. 
...

Full Content

Release Steps

The process can be summarized as:


	Update your Subversion workspace
	Manually update the tapestry version in the source code of the Tapestry archetype (found in quickstart/src/main/resources/archetype-resources/*) to the version number to be released
	mvn release:prepare
	mvn release:perform
	Generate and upload Binary / Source distributions
	
		The ant build script creates the distributions
		There's some manual work to sign and upload the distributions
	
	
	Login to Nexus, 'close' the automatically created staging repository and note its url
	Use the Manage Versions page in JIRA to add a new release (the new development release)
	Generate HTML Release Notes for the release
	
		Create a new child page of Release Notes
		Paste the HTML content into the new page (you'll have to use the {html} macro)
		Update Release Notes to point to the new page
	
	
	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 directory
	Once files reach all mirrors, update the Downloads Page
	
		Dont forget to change the version number to the new release
		Dont forget to link to the new release's Release Notes page
	
	




Be aware that Maven will perform some automatic Subversion commits, and even create the new release tag for you! Make
sure to get those version numbers right; I've found to my dismay that it can be tricky to correct this after-the-fact.

Notes

mvn release:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version). If it's one of your first releases, consider trying mvn release:prepare -DdryRun=true and manually observing the differences in the poms (this command will not commit the updated poms - it'll just generate them). See the Maven documentation for more details.

The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory.

The correct response to this prompt:

What is the SCM release tag or label for "Tapestry 5 Project"

is

5.X.X

This reflects that Tapestry stores its SVN tags in a slightly weird way (that made perfect sense at the time).

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









[CONF] Apache Tapestry Release Process

2010-09-28 Thread confluence







Release Process
Page  added by Howard M. Lewis Ship

 

 The process can be summarized as:

	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





   
Change Notification Preferences
   
   View Online
   








[CONF] Apache Tapestry Release Process

2010-09-28 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
# SSH to people.apache.org and copy the Binary / Source distributions to the right diretory # Once files reach all mirrors, update the Downloads Page 
 A template for the vote e-mail:   {noformat} Ive 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.  Ive 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, Ill 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 Ill move the voted artifacts into place and send out appropriate notifications.  {noformat}  I often embellish this template with extra detail. 

Full Content

The process can be summarized as:

	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



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









[CONF] Apache Tapestry Release Process

2010-09-28 Thread 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









[CONF] Apache Tapestry Release Process

2010-09-28 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (7)
 



 h2. Release Steps  
The process can be summarized as:  
...
# 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. 
h2. Notes 
 
A template for the vote e-mail: 
{{mvn:prepare}} does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version, and incrementing the version number for the new development version). 
 
The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory. 
 
The correct response to this prompt:  {indent}What is the SCM release tag or label for Tapestry 5 Project{indent}  is  {indent}releases/5.X.X{indent}  This reflects that Tapestry stores its SVN tags in a slightly weird way (that made _perfect_ sense at the time).  h2. A template for the vote e-mail:   
{noformat} Ive created and uploaded a release of Tapestry 5.x.x, ready to be 
...

Full Content


Release Steps

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



Notes

mvn:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version).

The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory.

The correct response to this prompt:

What is the SCM release tag or label for "Tapestry 5 Project"

is

releases/5.X.X

This reflects that Tapestry stores its SVN tags in a slightly weird way (that made perfect sense at the time).

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









[CONF] Apache Tapestry Release Process

2010-09-28 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
is  
{indent}releases/5.X.X{indent} 
 This reflects that Tapestry stores its SVN tags in a slightly weird way (that made _perfect_ sense at the time). 
...

Full Content

Release Steps

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



Notes

mvn:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version).

The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory.

The correct response to this prompt:

What is the SCM release tag or label for "Tapestry 5 Project"

is

5.X.X

This reflects that Tapestry stores its SVN tags in a slightly weird way (that made perfect sense at the time).

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









[CONF] Apache Tapestry Release Process

2010-09-28 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
 {{mvn:prepare}} does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version, 
and incrementing the version number for the new development version). See [the Maven documentation|http://maven.apache.org/plugins/maven-release-plugin/introduction.html] for more details. 
 The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory. 
...

Full Content

Release Steps

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



Notes

mvn:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version). See the Maven documentation for more details.

The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory.

The correct response to this prompt:

What is the SCM release tag or label for "Tapestry 5 Project"

is

5.X.X

This reflects that Tapestry stores its SVN tags in a slightly weird way (that made perfect sense at the time).

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









[CONF] Apache Tapestry Release Process

2010-09-28 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
# Once files reach all mirrors, update the Downloads Page  
{warning} Be aware that Maven will perform some automatic Subversion checkins, and even create the new tag for you! Make sure to get those version numbers right; Ive found to my dismay that it can be tricky to correct this after-the-fact. {warning}  
h2. Notes  
...

Full Content

Release Steps

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



Be aware that Maven will perform some automatic Subversion checkins, and even create the new tag for you! Make
sure to get those version numbers right; I've found to my dismay that it can be tricky to correct this after-the-fact.

Notes

mvn:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version). See the Maven documentation for more details.

The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory.

The correct response to this prompt:

What is the SCM release tag or label for "Tapestry 5 Project"

is

5.X.X

This reflects that Tapestry stores its SVN tags in a slightly weird way (that made perfect sense at the time).

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









[CONF] Apache Tapestry Release Process

2010-09-28 Thread confluence







Release Process
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
The process can be summarized as:  
{note:title=TODO} JIRA: close out release, generate release notes! {note}  
# Update your _Subversion_ workspace # mvn release:prepare 
...

Full Content

Release Steps

The process can be summarized as:

TODOJIRA: close out release, generate release notes!


	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



Be aware that Maven will perform some automatic Subversion commits, and even create the new release tag for you! Make
sure to get those version numbers right; I've found to my dismay that it can be tricky to correct this after-the-fact.

Notes

mvn:prepare does a very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,
and incrementing the version number for the new development version). See the Maven documentation for more details.

The Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout into a new directory.

The correct response to this prompt:

What is the SCM release tag or label for "Tapestry 5 Project"

is

5.X.X

This reflects that Tapestry stores its SVN tags in a slightly weird way (that made perfect sense at the time).

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