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 Tue, 28 Sep 2010 23:11:00 GMT
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1810/9/12/_/styles/combined.css?spaceKey=TAPESTRY&amp;forWysiwyg=true"
<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
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~hlship">Howard
M. Lewis Ship</a>
                         <h4>Changes (2)</h4>
<div id="page-diffs">
            <table class="diff" cellpadding="0" cellspacing="0">
            <tr><td class="diff-unchanged" >The process can be summarized as:
            <tr><td class="diff-added-lines" style="background-color: #dfd;">#
Update your _Subversion_ workspace <br></td></tr>
            <tr><td class="diff-unchanged" ># mvn release:prepare <br>#
mvn release:perform <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" ># Once files reach all mirrors, update
the Downloads Page <br> <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">Note
the first step; the Maven code assumes it is executing inside a Subversion (not Git+SVN) workspace.
<br> <br></td></tr>
            <tr><td class="diff-unchanged" >A template for the vote e-mail: <br>
            <tr><td class="diff-snipped" >...<br></td></tr>
</div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <p>The process can be summarized as:</p>
	<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
	<li>Once files reach all mirrors, update the Downloads Page</li>

<p>Note the first step; the Maven code assumes it is executing inside a Subversion (not
Git+SVN) workspace.</p>

<p>A template for the vote e-mail:</p>

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


and the Maven artifacts staged to:


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:


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.


<p>I often embellish this template with extra detail.</p>
        <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>
        <a href="https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Process">View
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=23339205&revisedVersion=3&originalVersion=2">View

View raw message