tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Tapestry > Release Process
Date Wed, 29 Sep 2010 00:10:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1810/9/12/_/styles/combined.css?spaceKey=TAPESTRY&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Process">Release
Process</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~hlship">Howard
M. Lewis Ship</a>
    </h4>
        <br/>
                         <h4>Changes (1)</h4>
                                 
    
<div id="page-diffs">
            <table class="diff" cellpadding="0" cellspacing="0">
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" > <br>{{mvn:prepare}} does a
very good job at guessing the right version numbers (i.e., stripping off the -SNAPSHOT suffix
for the release version, <br></td></tr>
            <tr><td class="diff-changed-lines" >and incrementing the version number
for the new development version). <span class="diff-added-words"style="background-color:
#dfd;">See [the Maven documentation|http://maven.apache.org/plugins/maven-release-plugin/introduction.html]
for more details.</span> <br></td></tr>
            <tr><td class="diff-unchanged" > <br>The Maven code assumes
it is executing inside a Subversion (not Git+SVN) workspace. I often create a fresh checkout
into a new directory. <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
        </table>
</div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h2><a name="ReleaseProcess-ReleaseSteps"></a>Release Steps</h2>

<p>The process can be summarized as:</p>

<ol>
	<li>Update your <em>Subversion</em> workspace</li>
	<li>mvn release:prepare</li>
	<li>mvn release:perform</li>
	<li>Generate and upload Binary / Source distributions</li>
	<li>Login to Nexus, 'close' automatically created staging repository and note its url.</li>
	<li>Send vote email ... 3 days pass</li>
	<li>Login to Nexus and promote the release</li>
	<li>SSH to people.apache.org and copy the Binary / Source distributions to the right
diretory</li>
	<li>Once files reach all mirrors, update the Downloads Page</li>
</ol>


<h2><a name="ReleaseProcess-Notes"></a>Notes</h2>

<p><tt>mvn:prepare</tt> does a very good job at guessing the right version
numbers (i.e., stripping off the -SNAPSHOT suffix for the release version,<br/>
and incrementing the version number for the new development version). See <a href="http://maven.apache.org/plugins/maven-release-plugin/introduction.html"
class="external-link" rel="nofollow">the Maven documentation</a> for more details.</p>

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

<p>The correct response to this prompt:</p>

<div class="indent20 inline" style="margin-left: 20px;"><style type="text/css">div.inline
p:first-child { display: inline; }</style><p>What is the SCM release tag or label
for "Tapestry 5 Project"</p></div>

<p>is</p>

<div class="indent20 inline" style="margin-left: 20px;"><style type="text/css">div.inline
p:first-child { display: inline; }</style><p>5.X.X</p></div>

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

<h2><a name="ReleaseProcess-Atemplateforthevoteemail%3A"></a>A template
for the vote e-mail:</h2>


<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>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.

</pre>
</div></div>

<p>I often embellish this template with extra detail.</p>
    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Process">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=23339205&revisedVersion=7&originalVersion=6">View
Changes</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message