Author: buildbot
Date: Sat Dec 19 21:20:15 2015
New Revision: 975960
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/release-process.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/release-process.html
==============================================================================
--- websites/production/tapestry/content/release-process.html (original)
+++ websites/production/tapestry/content/release-process.html Sat Dec 19
21:20:15 2015
@@ -142,7 +142,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-GeneratetheRelease">Generate the Release</h3><ul><li>Update
your workspace to the release branch<ul><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></ul></li><li><span style="line-height:
1.4285715;">Run the build using </span><code style="line-height:
1.4285715;">gradle generateRelease</code><br clear="none"><ul><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</l
i></ul></li><li>Tag the release in Git, then push the changes up to the Apache
repository:<ul><li><code>git tag 5.x</code></li><li><code>git push
--tags</code></li></ul></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></ul><h3
id="ReleaseProcess-CommittheArchives">Commit the Archives</h3><ul><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>)<ul><li>Use the full version number as
the commit message, e.g., <em>5.4-beta-26</em></li></ul></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></ul><h3
id="ReleaseProcess-BumptheVersionNu
mber">Bump the Version
Number</h3><ul><li>Update <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></ul><h3 id="ReleaseProcess-SendVote">Send
Vote</h3><ul><li><span style="line-height: 1.4285715;">Send vote
email</span></li><li><span style="line-height: 1.4285715;"><strong>Wait 3
days</strong><br clear="none"></span></li><li><span style="line-height:
1.4285715;">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 style="line-height: 1.4285715;">Only
PMC members may cast binding votes</span></li></ul><h3
id="ReleaseProcess-UpdateJIRAandgeneratereleasenotes"><span>Update JIRA and
generate release notes</span><span style="line-height:
22.857143px;"> </span></h3><ul><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 often 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<ul><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 hav
e 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></ul></li></ul><h3
id="ReleaseProcess-ReleasetheMavenArtifacts"><span style="line-height:
22.857143px;">Release the Maven Artifacts</span></h3><ul><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<ul><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></ul></li><li>Releasing will ultimately get the artifacts up to the
central Maven repository</li></ul><h3
id="ReleaseProcess-ReleasetheArchives">Release the Archives</h3><ul><li>Copy
the release archives files (including checksums and GPG signatures) t
o 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></ul><h3
id="ReleaseProcess-ReleasetheKraken">Release the Kraken</h3><ul><li>This occurs
automatically</li></ul><h3 id="ReleaseProcess-Wait">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-UpdateDocumentation"><span style="line-height:
1.4285715;">Update Documentation</span></h3><ul><li><span style="line-height:
1.4285715;">Update the release number listed in the following pages in the
Confluence wiki:</span><br clear="none"><ul><li><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="g
etting-started.html">Getting Started</a> page: Tapestry version number in the
archetype</li></ul></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><code>archetype-catalog.xml</code><span> to
add or update a new entry for the release</span></li><li><span
style="line-height: 1.4285715;">Update the release number and date
inside </span><code style="line-height: 1.4285715;">doap.rdf</code><span
style="line-height: 1.4285715;">  (this is a </span><a
class="external-link" href="https://projects.apache.org/doap.html";
style="line-height: 1.4285715;">description file</a><span style="line-height:
1.4285715;"> for the project)</span></li><li><span style="line-height:
1.4285715;"><code>svn commit</code></span></li></ul><h3
id="ReleaseProcess-Done!"><span style="line-height:
1.4285715;">Done!</span></h3><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 panelContent 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 style="line-height:
1.4285715;">Run the build using </span><code style="line-height:
1.4285715;">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 wo
rkspace</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>Update <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 style="line-height: 1.4285715;">Send vote
email</span></li><li><span style="line-height: 1.4285715;"><strong>Wait 3
days</strong><br clear="none"></span></li><li><span style="line-height:
1.4285715;">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 style="line-height: 1.4285715;">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 style="line-height:
22.857143px;"> </span></h3><ol><li><span>Use the
60;</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 often 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 style="line-height:
22.857143px;">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 (i
ncluding 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.ReleasetheKraken">8. Release the
Kraken</h3><ul><li>This occurs automatically</li></ul><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 style="line-height:
1.4285715;">10. Update Documentation</span></h3><ol><li><span
style="line-height: 1.4285715;">Update the release number listed in the
following pages in the Confluence wiki:</span><br clear="none"><ol><li><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 num
ber 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><code>archetype-catalog.xml</code><span> to
add or update a new entry for the release</span></li><li><span
style="line-height: 1.4285715;">Update the release number and date
inside </span><code style="line-height: 1.4285715;">doap.rdf</code><span
style="line-height: 1.4285715;">  (this is a </span><a
class="external-link" href="https://projects.apache.org/doap.html";
style="line-height: 1.4285715;">description file</a><span style="line-height:
1.4285715;"> for the project)</span></li><li><span style="line-height:
1.4285715;"><code>svn commit</code></span></li></ol><h3
id="ReleaseProcess-11.Blog&Tweet"><span>11. Blog &
Tweet</span></h3><ol><li><a href="https://cwik
i.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 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:
@@ -170,7 +170,7 @@ Only votes cast by Tapestry PMC members
from the community is highly valued. Please indicate whether your
vote is binding or not after your full name (as it will appear in
the end-of-vote summary).</pre>
-</div></div><p>I often embellish this template with extra
detail.</p><p>Lately, I append a text version of the JIRA release notes as
well.</p></div>
+</div></div><p>The release manager often embellishes this template with extra
detail.</p><p>It's also a nice touch to append a text version of the JIRA
release notes as well.</p></div>
</div>
<div class="clearer"></div>
