Author: gdaniels
Date: Tue Jun 12 10:58:05 2007
New Revision: 546576
URL: http://svn.apache.org/viewvc?view=rev&rev=546576
Log:
Introduce release process guidelines.
Added:
webservices/axis2/trunk/java/xdocs/release-process.html
Modified:
webservices/axis2/trunk/java/xdocs/guidelines.html
webservices/axis2/trunk/java/xdocs/navigation.xml
Modified: webservices/axis2/trunk/java/xdocs/guidelines.html
URL:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/guidelines.html?view=diff&rev=546576&r1=546575&r2=546576
==============================================================================
--- webservices/axis2/trunk/java/xdocs/guidelines.html (original)
+++ webservices/axis2/trunk/java/xdocs/guidelines.html Tue Jun 12 10:58:05 2007
@@ -6,7 +6,11 @@
</head>
<body>
-<h2>Mail Guideline</h2>
+<h2>Release Process</h2>
+
+<p>Click to read our <a href="release-process.html">Release Process
Guidelines</a>.</p>
+
+<h2>Mail Guidelines</h2>
<p>Every volunteer project obtains its strength from the people involved in
it. Mailing lists provide a simple and effective communication mechanism.</p>
Modified: webservices/axis2/trunk/java/xdocs/navigation.xml
URL:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/navigation.xml?view=diff&rev=546576&r1=546575&r2=546576
==============================================================================
--- webservices/axis2/trunk/java/xdocs/navigation.xml (original)
+++ webservices/axis2/trunk/java/xdocs/navigation.xml Tue Jun 12 10:58:05 2007
@@ -46,7 +46,8 @@
<item name="Overview" href="overview.html" />
<item name="Checkout the Source" href="svn.html" />
<item name="Mailing Lists" href="mail-lists.html" />
- <item name="Developer Guidelines" href="guidelines.html" />
+ <item name="Release Process" href="release-process.html"/>
+ <item name="Developer Guidelines" href="guidelines.html" />
<item name="Build the Site" href="siteHowTo.html" />
</menu>
<menu name="Project Information">
Added: webservices/axis2/trunk/java/xdocs/release-process.html
URL:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/release-process.html?view=auto&rev=546576
==============================================================================
--- webservices/axis2/trunk/java/xdocs/release-process.html (added)
+++ webservices/axis2/trunk/java/xdocs/release-process.html Tue Jun 12 10:58:05
2007
@@ -0,0 +1,56 @@
+<html>
+<head>
+ <meta http-equiv="content-type" content="">
+ <title>Axis2 Release Process</title>
+ <link href="css/axis-docs.css" rel="stylesheet" type="text/css" media="all">
+</head>
+
+<body>
+<h2>Release Process</h2>
+
+<h3>Cutting a branch</h3>
+
+<ul>
+ <li>When a release is ready to go, release manager (RM) puts forward a
release plan as per standard Apache process, including dates. This gets VOTEd
on by the committers. During this period the trunk is still the only relevant
source base.</li>
+
+<li> As soon as a release is approved (or even before), RM should add the new
version into JIRA as a target.
+
+<li> At the point where we would normally do the "code freeze" for a release,
the RM cuts a branch named for the release. This branch is where the release
candidates and releases will happen.
+
+<li> Ideally a release branch is only around for a week or maybe two before
the release happens.
+
+<li> The only things that should EVER get checked into the release branch are
- 1) bug fixes targeted at the release, 2) release-specific updates
(documentation, SNAPSHOT removal, etc). In particular new functionality does
not go here unless it is a solution to a JIRA report targeted at the release.
+
+<li> Normal development continues on the trunk.
+
+</ul>
+
+<h3>Dependencies and branches</h3>
+
+<ul>
+<li> The trunk should always be "cutting edge" and as such should usually be
pointing at SNAPSHOT versions of all dependencies. This allows for continuous
integration with our partner projects.
+
+<li> Soon after a release branch is cut, the RM is responsible for removing
ALL dependencies on SNAPSHOT versions and replacing them with officially
released versions. This change happens only on the release branch.
+</ul>
+
+<h3>Managing change and issue resolution with a release branch</h3>
+<ul>
+<li> The RM goes through JIRA issues and sets "fix for" to point to both
"NIGHTLY" and the new branched release number for the fixes that are targeted
for the release after the branch is cut.
+
+<li> In general, the assignee/coder fixes JIRA issues or makes other changes
*on the trunk*. If the JIRA issue is targeted at the release, or upon coder's
discretion, they then merge the fix over to the release branch.
+
+<li> This way the trunk is ALWAYS up-to-date, and we don't have to worry about
losing fixes that have only been made on the release branch.
+
+<li> When the assignee resolves an issue, they confirm it's been fixed in both
branches, if appropriate.
+</ul>
+
+<h3>Checking changes into the branch</h3>
+
+<ul>
+<li> If bug fixes are needed later for a release which has long since happened
(to fix user issues, etc), those fixes generally should also happen on the
trunk first assuming the problem still exists on the trunk.
+
+<li> There are only two cases where we would ever check anything into the
branch without first checking it into the trunk. 1) Release specific items
(release number references, release notes, removal of SNAPSHOTs), and 2) if the
trunk has moved on in some incompatible way.
+</ul>
+
+</body>
+</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
