You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by bu...@apache.org on 2018/02/19 20:20:17 UTC
svn commit: r1025622 [4/4] - in /websites/production/tapestry/content: ./
cache/
Modified: websites/production/tapestry/content/release-process.html
==============================================================================
--- websites/production/tapestry/content/release-process.html (original)
+++ websites/production/tapestry/content/release-process.html Mon Feb 19 20:20:17 2018
@@ -153,7 +153,7 @@ signing.secretKeyRingFile=.../.gnupg/sec
signing.password=...
apacheArchivesFolder=.../tapestry-dev</pre>
-</div></div><p>You can find your keyId using <code>gpg --list-keys</code>.</p><p> The apacheArchivesFolder should be the full path to your dev archives workspace. The build will copy files to this folder; see further notes below.</p><h2 id="ReleaseProcess-ReleaseSteps">Release Steps</h2><h3 id="ReleaseProcess-1.GeneratetheRelease">1. Generate the Release</h3><ol><li>Update your workspace to the release branch<ol><li>For current work, the release branch is <em>master</em></li><li>When creating bug fix releases for older releases, the branch will match the release, e.g., <em>5.3</em></li></ol></li><li><span>Run the build using </span><code>gradle generateRelease</code><br clear="none"><ol><li>This will create, sign, and upload JAR files and other artifacts to the Nexus repository</li><li>It will also create, sign, and copy the source, binary, and documentation archives to your dev archives workspace</li></ol></li><li>Tag the release in Git, then push the
changes up to the Apache repository:<ol><li><code>git tag 5.x</code></li><li><code>git push --tags</code></li></ol></li><li>Login to <a class="external-link" href="https://repository.apache.org/index.html#stagingRepositories">Nexus</a> and <strong>close</strong> the automatically created staging repository</li></ol><h3 id="ReleaseProcess-2.CommittheArchives">2. Commit the Archives</h3><ol><li>The build will have copied archive files to your dist workspace</li><li><code>svn add</code> the new files</li><li><code>svn commit</code> to copy the files up to Apache (this is <em>slow</em>)<ol><li>Use the full version number as the commit message, e.g., <em>5.4-beta-26</em></li></ol></li><li>You can verify the files via the web: <a class="external-link" href="https://dist.apache.org/repos/dist/dev/tapestry">https://dist.apache.org/repos/dist/dev/tapestry</a></li></ol><h3 id="ReleaseProcess-3.BumptheVersionNumber">3. Bump the Version Number</h3><ol><li>Up
date <code>build.gradle</code> to increment the version number</li><li>Increment the minor version number (inside the tapestryVersion method, near the top of the file)</li><li><p>Commit and push the changes</p></li></ol><h3 id="ReleaseProcess-4.SendVote">4. Send Vote</h3><ol><li><span>Send vote email</span></li><li><span><strong>Wait 3 days</strong><br clear="none"></span></li><li><span>The vote is successful if there are at least three <strong>+1</strong>'s and more <strong>+1</strong> than <strong>-1</strong></span></li><li><span>Only PMC members may cast binding votes</span></li></ol><h3 id="ReleaseProcess-5.UpdateJIRAandgeneratereleasenotes"><span>5. Update JIRA and generate release notes</span><span> </span></h3><ol><li><span>Use the </span><a class="external-link" href="https://issues.apache.org/jira/plugins/servlet/project-config/TAP5/versions">Manage Versions page</a><span> in JIRA to add a new version (this is often not necessary as it is ofte
n created by someone earlier)</span></li><li><strong>Release</strong> the version, moving outstanding issues to the next version</li><li>Generate HTML Release Notes<ol><li>Visit the <a class="external-link" href="https://issues.apache.org/jira/browse/TAP5#selectedTab=com.atlassian.jira.plugin.system.project:versions-panel&subset=-1">TAP5 Versions pages in JIRA</a></li><li>Choose the correct version number</li><li>Click "Release Notes" (upper right corner of the page)</li><li>Create a new Confluence child page of <a href="release-process.html">Release Process</a> (it may already exist)</li><li>Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)</li><li>Paste the HTML release notes content into the new page (you'll have to use the {html} macro)</li><li>Rename the "Bug" heading to "Bugs Fixed", "Improvement" to "Improvements Made", "New Feature" to "New Features Added"</li><li>Update <a href="release-p
rocess.html">Release Process</a> index page to point to the new page</li></ol></li></ol><h3 id="ReleaseProcess-6.ReleasetheMavenArtifacts"><span>6. Release the Maven Artifacts</span></h3><ol><li>Login to <a class="external-link" href="https://repository.apache.org/index.html#stagingRepositories">Nexus</a> and <strong>release</strong> the version's repository<ol><li>Enter "Apache Tapestry 5.x" (adjust as necessary) for the message</li><li>The version will disappear from the list of repositories after releasing it</li></ol></li><li>Releasing will ultimately get the artifacts up to the central Maven repository</li></ol><h3 id="ReleaseProcess-7.ReleasetheArchives">7. Release the Archives</h3><ol><li>Copy the release archives files (including checksums and GPG signatures) to the release archives workspace</li><li>Change to the release archives workspace</li><li><code>svn add</code> and<code>svn commit</code>, as with the dev archives workspace</li></ol><h3 id="ReleaseProcess-8.Rele
asetheJavadocs">8. Release the Javadocs</h3><ol><li>Run the "aggregateJavadoc" gradle task</li><li>Copy the resulting files from build/documentation/javadocs/* to a version-numbered subdirectory of your site <em>content</em> workspace (see Prerequisites at the top of this page)</li><li>svn commit those new javadoc files</li><li>Update the "current" symbolic link under the content directory to point to new version-numbered directory. For example, if "current" is a symbolic link to "5.4" and you want to change it to "5.5", do this:<br clear="none"><ul><li>rm current</li><li>ln -s 5.5 current</li><li>svn commit -m "Updated javadocs current symbolic link" current</li></ul></li></ol><h3 id="ReleaseProcess-9.Wait">9. Wait</h3><ul><li>You must wait at least 24 hours for the archives and artifacts to be distributed to the Apache mirrors and to the central Maven repository</li></ul><h3 id="ReleaseProcess-10.UpdateDocumentation"><span>10. Update Documentation</span></h3><ol><li><span>Update t
he release number listed in the following pages in the Confluence wiki:</span><br clear="none"><ol><li><a href="release-process.html">Release Process</a> page</li><li>(Optional) Tutorial <a href="release-process.html">Release Process</a> page: Tapestry version number in the archetype</li><li>(Optional) <a href="release-process.html">Release Process</a> page: Tapestry version number in the archetype</li></ol></li><li><span>Change to the site content workspace</span></li><li><code>svn update</code> to get any recent changes</li><li><span>Edit </span><a class="external-link" href="https://svn.apache.org/repos/infra/websites/production/tapestry/content/archetype-catalog.xml"><span> </span><code>archetype-catalog.xml</code><span> </span></a><span>to add or update a new entry for the release</span></li><li><span>Update the release number and date inside </span><code>doap.rdf</code><span>  (this is a </span><a class="external-link" href="https://projects.
apache.org/doap.html">description file</a><span> for the project)</span></li><li><span><code>svn commit</code></span></li></ol><h3 id="ReleaseProcess-11.Blog&Tweet"><span>11. Blog & Tweet</span></h3><ol><li><a href="https://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=TAPESTRY"><span>Write a blog post</span></a><span> in Confluence announcing the release.</span></li><li><span>Send an email to the <em>users</em> mailing list announcing the release.<br clear="none"></span></li><li><span>Send out a tweet (using the <a class="external-link" href="https://twitter.com/apachetapestry" rel="nofollow"><em>ApacheTapestry</em></a> Twitter account) announcing the release.<br clear="none"></span></li></ol><h3 id="ReleaseProcess-Done!"><span>Done!</span></h3><p><span><br clear="none"></span></p><hr><h2 id="ReleaseProcess-Atemplateforthevotee-mail:">A template for the vote e-mail:</h2><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panel
Content pdl">
+</div></div><p>You can find your keyId using <code>gpg --list-keys</code>.</p><p> The apacheArchivesFolder should be the full path to your dev archives workspace. The build will copy files to this folder; see further notes below.</p><h2 id="ReleaseProcess-ReleaseSteps">Release Steps</h2><h3 id="ReleaseProcess-1.GeneratetheRelease">1. Generate the Release</h3><ol><li>Update your workspace to the release branch<ol><li>For current work, the release branch is <em>master</em></li><li>When creating bug fix releases for older releases, the branch will match the release, e.g., <em>5.3</em></li></ol></li><li><span>Run the build using </span><code>gradle generateRelease</code><br clear="none"><ol><li>This will create, sign, and upload JAR files and other artifacts to the Nexus repository</li><li>It will also create, sign, and copy the source, binary, and documentation archives to your dev archives workspace</li></ol></li><li>Tag the release in Git, then push the
changes up to the Apache repository:<ol><li><code>git tag 5.x</code></li><li><code>git push --tags</code></li></ol></li><li>Login to <a class="external-link" href="https://repository.apache.org/index.html#stagingRepositories">Nexus</a> and <strong>close</strong> the automatically created staging repository</li></ol><h3 id="ReleaseProcess-2.CommittheArchives">2. Commit the Archives</h3><ol><li>The build will have copied archive files to your dist workspace</li><li><code>svn add</code> the new files</li><li><code>svn commit</code> to copy the files up to Apache (this is <em>slow</em>)<ol><li>Use the full version number as the commit message, e.g., <em>5.4-beta-26</em></li></ol></li><li>You can verify the files via the web: <a class="external-link" href="https://dist.apache.org/repos/dist/dev/tapestry">https://dist.apache.org/repos/dist/dev/tapestry</a></li></ol><h3 id="ReleaseProcess-3.BumptheVersionNumber">3. Bump the Version Number</h3><ol><li>Up
date <code>build.gradle</code> to increment the version number</li><li>Increment the minor version number (inside the tapestryVersion method, near the top of the file)</li><li><p>Commit and push the changes</p></li></ol><h3 id="ReleaseProcess-4.SendVote">4. Send Vote</h3><ol><li><span>Send vote email</span></li><li><span><strong>Wait 3 days</strong><br clear="none"></span></li><li><span>The vote is successful if there are at least three <strong>+1</strong>'s and more <strong>+1</strong> than <strong>-1</strong></span></li><li><span>Only PMC members may cast binding votes</span></li></ol><h3 id="ReleaseProcess-5.UpdateJIRAandgeneratereleasenotes"><span>5. Update JIRA and generate release notes</span><span> </span></h3><ol><li><span>Use the </span><a class="external-link" href="https://issues.apache.org/jira/plugins/servlet/project-config/TAP5/versions">Manage Versions page</a><span> in JIRA to add a new version (this is often not necessary as it is ofte
n created by someone earlier)</span></li><li><strong>Release</strong> the version, moving outstanding issues to the next version</li><li>Generate HTML Release Notes<ol><li>Visit the <a class="external-link" href="https://issues.apache.org/jira/browse/TAP5#selectedTab=com.atlassian.jira.plugin.system.project:versions-panel&subset=-1">TAP5 Versions pages in JIRA</a></li><li>Choose the correct version number</li><li>Click "Release Notes" (upper right corner of the page)</li><li>Create a new Confluence child page of <a href="release-notes.html">Release Notes</a> (it may already exist)</li><li>Update with text about any unusual aspects of the upgrade (especially, non-backwards compatible changes)</li><li>Paste the HTML release notes content into the new page (you'll have to use the {html} macro)</li><li>Rename the "Bug" heading to "Bugs Fixed", "Improvement" to "Improvements Made", "New Feature" to "New Features Added"</li><li>Update <a href="release-notes.html
">Release Notes</a> index page to point to the new page</li></ol></li></ol><h3 id="ReleaseProcess-6.ReleasetheMavenArtifacts"><span>6. Release the Maven Artifacts</span></h3><ol><li>Login to <a class="external-link" href="https://repository.apache.org/index.html#stagingRepositories">Nexus</a> and <strong>release</strong> the version's repository<ol><li>Enter "Apache Tapestry 5.x" (adjust as necessary) for the message</li><li>The version will disappear from the list of repositories after releasing it</li></ol></li><li>Releasing will ultimately get the artifacts up to the central Maven repository</li></ol><h3 id="ReleaseProcess-7.ReleasetheArchives">7. Release the Archives</h3><ol><li>Copy the release archives files (including checksums and GPG signatures) to the release archives workspace</li><li>Change to the release archives workspace</li><li><code>svn add</code> and<code>svn commit</code>, as with the dev archives workspace</li></ol><h3 id="ReleaseProcess-8.ReleasetheJavadocs">8.
Release the Javadocs</h3><ol><li>Run the "aggregateJavadoc" gradle task</li><li>Copy the resulting files from build/documentation/javadocs/* to a version-numbered subdirectory of your site <em>content</em> workspace (see Prerequisites at the top of this page)</li><li>svn commit those new javadoc files</li><li>Update the "current" symbolic link under the content directory to point to new version-numbered directory. For example, if "current" is a symbolic link to "5.4" and you want to change it to "5.5", do this:<br clear="none"><ul><li>rm current</li><li>ln -s 5.5 current</li><li>svn commit -m "Updated javadocs current symbolic link" current</li></ul></li></ol><h3 id="ReleaseProcess-9.Wait">9. Wait</h3><ul><li>You must wait at least 24 hours for the archives and artifacts to be distributed to the Apache mirrors and to the central Maven repository</li></ul><h3 id="ReleaseProcess-10.UpdateDocumentation"><span>10. Update Documentation</span></h3><ol><li><span>Update the release number
listed in the following pages in the Confluence wiki:</span><br clear="none"><ol><li class="confluence-link"><a href="download.html">Download</a> page</li><li>(Optional) Tutorial <a href="creating-the-skeleton-application.html">Creating The Skeleton Application</a> page: Tapestry version number in the archetype</li><li>(Optional) <a href="getting-started.html">Getting Started</a> page: Tapestry version number in the archetype</li></ol></li><li><span>Change to the site content workspace</span></li><li><code>svn update</code> to get any recent changes</li><li><span>Edit </span><a class="external-link" href="https://svn.apache.org/repos/infra/websites/production/tapestry/content/archetype-catalog.xml"><span> </span><code>archetype-catalog.xml</code><span> </span></a><span>to add or update a new entry for the release</span></li><li><span>Update the release number and date inside </span><code>doap.rdf</code><span>  (this is a </span><a class="
external-link" href="https://projects.apache.org/doap.html">description file</a><span> for the project)</span></li><li><span><code>svn commit</code></span></li></ol><h3 id="ReleaseProcess-11.Blog&Tweet"><span>11. Blog & Tweet</span></h3><ol><li><a href="https://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=TAPESTRY"><span>Write a blog post</span></a><span> in Confluence announcing the release.</span></li><li><span>Send an email to the <em>users</em> mailing list announcing the release.<br clear="none"></span></li><li><span>Send out a tweet (using the <a class="external-link" href="https://twitter.com/apachetapestry" rel="nofollow"><em>ApacheTapestry</em></a> Twitter account) announcing the release.<br clear="none"></span></li></ol><h3 id="ReleaseProcess-Done!"><span>Done!</span></h3><p><span><br clear="none"></span></p><hr><h2 id="ReleaseProcess-Atemplateforthevotee-mail:">A template for the vote e-mail:</h2><div class="code panel pdl" style="border-widt
h: 1px;"><div class="codeContent panelContent pdl">
<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">I've created and uploaded a release of Tapestry 5.x, ready to be voted upon.
The source, binary, and documentation archives have been uploaded to:
Modified: websites/production/tapestry/content/support.html
==============================================================================
--- websites/production/tapestry/content/support.html (original)
+++ websites/production/tapestry/content/support.html Mon Feb 19 20:20:17 2018
@@ -67,7 +67,7 @@
</div>
<div id="content">
- <div id="ConfluenceContent"><p>Apache Tapestry is an open source project and as such, supported by the community. Even if you are looking for commercial support, your best bet for support is to first subscribe to Apache Tapestry user mailing list and ask there. Read more about how to <a href="support.html">get involved</a>.</p><h3 id="Support-CommercialTrainingandSupport">Commercial Training and Support</h3><p>Training on Tapestry and Support is available directly from the source: the Tapestry project committers:</p><ul><li><a class="external-link" href="http://www.arsmachina.com.br/services" rel="nofollow">Thiago H. de Paula Figueriredo</a>: Provides training and support on Tapestry and related technologies including Spring and Hibernate</li></ul><h3 id="Support-CommunitySupport">Community Support</h3><p>Like all Apache projects, Tapestry uses mailing lists for most communication. You can subscribe by sending e-mail to the addresses below. For each list, there are
subscribe, unsubscribe, and archive links. All Tapestry users are welcome to subscribe to any of these lists, however questions on how to <em>use</em> Tapestry in your application are best sent to the <em>user</em> mailing list.</p><p>Please note that the Nabble archives are set to read-only and don't allow for posting or answering using Nabble's web interface. You have to subscribe to the mailing list in order to post.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><th colspan="1" rowspan="1" class="confluenceTh"><p>Subscribe</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Unsubscribe</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Apache Archive</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Nabble Archive</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>MarkMail Archive</p></th></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Tapest
ry User List</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:users-subscribe@tapestry.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:users-unsubscribe@tapestry.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://mail-archives.apache.org/mod_mbox/tapestry-users/">mail-archives.apache.org</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.1045711.n5.nabble.com/Tapestry-User-f2375125.html" rel="nofollow">www.nabble.com</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.markmail.org/search/?q=list%3Aorg.apache.tapestry.users" rel="nofollow">tapestry.markmail.org</a></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Tap
estry Developer List</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:dev-subscribe@tapestry.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:dev-unsubscribe@tapestry.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://mail-archives.apache.org/mod_mbox/tapestry-dev/">mail-archives.apache.org</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.1045711.n5.nabble.com/Tapestry-Dev-f2438278.html" rel="nofollow">www.nabble.com</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.markmail.org/search/?q=list%3Aorg.apache.tapestry.dev" rel="nofollow">tapestry.markmail.org</a></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Tape
stry Commits List</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:commits-subscribe@tapestry.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:commits-unsubscribe@tapestry.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://mail-archives.apache.org/mod_mbox/tapestry-commits/">mail-archives.apache.org</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.markmail.org/search/?q=list%3Aorg.apache.tapestry.commits" rel="nofollow">tapestry.markmail.org</a></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Search Multiple Lists</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>-</p></td><td colspan="1" rowspan="1" c
lass="confluenceTd"><p>-</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.1045711.n5.nabble.com/" rel="nofollow">www.nabble.com</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.markmail.org/search/?q=#query:+page:1+state:facets" rel="nofollow">tapestry.markmail.org</a></p></td></tr></tbody></table></div></div>
+ <div id="ConfluenceContent"><p>Apache Tapestry is an open source project and as such, supported by the community. Even if you are looking for commercial support, your best bet for support is to first subscribe to Apache Tapestry user mailing list and ask there. Read more about how to <a href="community.html">get involved</a>.</p><h3 id="Support-CommercialTrainingandSupport">Commercial Training and Support</h3><p>Training on Tapestry and Support is available directly from the source: the Tapestry project committers:</p><ul><li><a class="external-link" href="http://www.arsmachina.com.br/services" rel="nofollow">Thiago H. de Paula Figueriredo</a>: Provides training and support on Tapestry and related technologies including Spring and Hibernate</li></ul><h3 id="Support-CommunitySupport">Community Support</h3><p>Like all Apache projects, Tapestry uses mailing lists for most communication. You can subscribe by sending e-mail to the addresses below. For each list, there a
re subscribe, unsubscribe, and archive links. All Tapestry users are welcome to subscribe to any of these lists, however questions on how to <em>use</em> Tapestry in your application are best sent to the <em>user</em> mailing list.</p><p>Please note that the Nabble archives are set to read-only and don't allow for posting or answering using Nabble's web interface. You have to subscribe to the mailing list in order to post.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><th colspan="1" rowspan="1" class="confluenceTh"><p>Subscribe</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Unsubscribe</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Apache Archive</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Nabble Archive</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>MarkMail Archive</p></th></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Tape
stry User List</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:users-subscribe@tapestry.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:users-unsubscribe@tapestry.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://mail-archives.apache.org/mod_mbox/tapestry-users/">mail-archives.apache.org</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.1045711.n5.nabble.com/Tapestry-User-f2375125.html" rel="nofollow">www.nabble.com</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.markmail.org/search/?q=list%3Aorg.apache.tapestry.users" rel="nofollow">tapestry.markmail.org</a></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>T
apestry Developer List</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:dev-subscribe@tapestry.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:dev-unsubscribe@tapestry.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://mail-archives.apache.org/mod_mbox/tapestry-dev/">mail-archives.apache.org</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.1045711.n5.nabble.com/Tapestry-Dev-f2438278.html" rel="nofollow">www.nabble.com</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.markmail.org/search/?q=list%3Aorg.apache.tapestry.dev" rel="nofollow">tapestry.markmail.org</a></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Ta
pestry Commits List</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:commits-subscribe@tapestry.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="mailto:commits-unsubscribe@tapestry.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://mail-archives.apache.org/mod_mbox/tapestry-commits/">mail-archives.apache.org</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.markmail.org/search/?q=list%3Aorg.apache.tapestry.commits" rel="nofollow">tapestry.markmail.org</a></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Search Multiple Lists</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>-</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>-</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.1045711.n5.nabble.com/" rel="nofollow">www.nabble.com</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a class="external-link" href="http://tapestry.markmail.org/search/?q=#query:+page:1+state:facets" rel="nofollow">tapestry.markmail.org</a></p></td></tr></tbody></table></div></div>
</div>
<div class="clearer"></div>
Modified: websites/production/tapestry/content/version-numbers.html
==============================================================================
--- websites/production/tapestry/content/version-numbers.html (original)
+++ websites/production/tapestry/content/version-numbers.html Mon Feb 19 20:20:17 2018
@@ -73,8 +73,7 @@
</p><div class="aui-message aui-message-info">
Added in 5.3
- Tapestry version numbering was change starting in release 5.3. Tapestry 5.2 and earlier used a different numbering scheme whose primary failing was that, from the version number, it was not obvious what the _stability_ of the version was.
-
+ Tapestry version numbering was change starting in release 5.3. Tapestry 5.2 and earlier used a different numbering scheme whose primary failing was that, from the version number, it was not obvious what the <em>stability</em> of the version was.
</div>This document describes Tapestry's version numbering system. This is important, as version numbers relate both to artifacts available for download, or from a Maven repository, and also to bugs recorded in the issue tracking system.<h1 id="VersionNumbers-TapestryReleaseNumbers">Tapestry Release Numbers</h1><p>Tapestry release numbers consist of a product version number, and release index number, seperated by periods, for example "5.3". The product version number, 5, is unlikely to change any time soon (it would indicate a non-backwards compatible rewrite of the framework, and we've had enough of that, thank you very much).</p><h1 id="VersionNumbers-TapestryStableReleaseVersions">Tapestry Stable Release Versions</h1><p>Tapestry stable releases use the name version number as the release number.</p><p>A bug fix release follows a stable release, when necessary. Bug fix releases add a sequence number to the product release number. Thus, the first bug fix release for Tapestry 5.3 wil
l be version 5.3.1, then 5.3.2, as necessary.</p><p>A bug fix release <em>replaces</em> the previous stable release.</p><h1 id="VersionNumbers-PreviewVersions">Preview Versions</h1><p>During the course of development of a release, there will be preview releases of non-final versions. A preview version consists of the product version, a stability term, and an index number, separated by dashes. The stability term is "alpha", "beta", or "rc".</p><p>The index number starts at 1. A preview version number might be "5.3-alpha-2", or "5.3-beta-1", for example. The index number resets back to one when the stability itself is upgraded.</p><p>"alpha" versions are not stable; the represent functionality in flux; classes and methods may be renamed or otherwise refactored between releases.</p><p>"beta" versions occur once main functionality is complete; they exist to fix bugs in both old and new functionality, and fill any gaps in functionality.</p><p>"rc" versions are "release candidates"; the f
unctionality should be solid; the point of a release candidate is to get wide exposure to the new codebase to ensure that the final release is free of bugs.</p><h1 id="VersionNumbers-PreviewPackages">Preview Packages</h1><p>A preview package may be created at any time. A tag is created in Git to label the exact source from which the preview package is generated. The preview package is built and uploaded to the Apache Nexus. Once uploaded, the master version number (in trunk) should be advanced to the next index number within the same stability series (example: "5.3-alpha-2" to "5.3-alpha-3").</p><p>The Apache Nexus URL for the preview package may be distributed on the Tapestry user mailing list. However, preview packages are deleted, not released. This is important ... preview packages are never released to the Maven Central repository, only final releases are distributed via Maven Central.</p><p>A stability vote may follow a preview package. This is to vote the code base up to the
next level of stability (to "beta", then "rc", then "stable"). This a lazy consensus vote.</p><h1 id="VersionNumbers-StableReleases">Stable Releases</h1><p>Once a version has been voted "stable", a release may be built and uploaded to the Apache Nexus. A stable release also includes additional non-Maven artifacts containing the project's source code, and additional<br clear="none"> artifacts containing JavaDoc or other reports. The other artifacts are distributed via the Apache Mirrors.</p><p>The vote for a release is a binding vote, requiring at least 3 +1 votes and no vetoes, as outlined in <a class="external-link" href="http://www.apache.org/foundation/voting.html">http://www.apache.org/foundation/voting.html</a></p><p>Following a successful release vote, the final release artifacts in the Apache Nexus repository may be released to the Maven Central repository, and the additional artifacts moved into place for download from the Apache distribution mirrors. This is also the point
at which the Tapestry wiki is updated to announce the new release (and provide proper links to it), as well as announcements on the Tapestry user mailing list and elsewhere.</p><p>Bug fix releases are follow-ons to stable releases. Bug fix versions automatically start at stability "rc", reflecting the fact that only localized bug fixes are expected to be included in such a release. Once all desired bug fixes are in place, a stability vote (to "stable") is followed by a release vote.</p></div>
</div>