You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ju...@apache.org on 2018/09/13 14:06:20 UTC
svn commit: r1840822 - in /subversion/site/publish/docs/community-guide:
releasing.part.html releasing.toc.html
Author: julianfoad
Date: Thu Sep 13 14:06:20 2018
New Revision: 1840822
URL: http://svn.apache.org/viewvc?rev=1840822&view=rev
Log:
* publish/docs/community-guide/releasing.part.html,
publish/docs/community-guide/releasing.toc.html
(release-branches): Organize some existing content into subsections.
Modified:
subversion/site/publish/docs/community-guide/releasing.part.html
subversion/site/publish/docs/community-guide/releasing.toc.html
Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1840822&r1=1840821&r2=1840822&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Sep 13 14:06:20 2018
@@ -1251,6 +1251,12 @@ minor release is a good time to start pr
that this is flexible, depending on what features are being
developed.</p>
+<div class="h3" id="before-branching">
+<h3>Preparing to create a new minor release branch
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#before-branching"
+ title="Link to this section">¶</a>
+</h3>
+
<ul>
<li><p>Review the <a href="/roadmap">Roadmap</a>. Should any of the outstanding
items be addressed before branching?</p></li>
@@ -1283,6 +1289,14 @@ developed.</p>
>tests against the incumbent minor release</a>.</p></li>
</ul>
+</div> <!-- before-branching -->
+
+<div class="h3" id="creating-branch">
+<h3>Creating a new minor release branch
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#creating-branch"
+ title="Link to this section">¶</a>
+</h3>
+
<p>Once people agree that a new release branch should be made, the
Release Manager creates it with the following procedure (substitute
A.B with the version you're preparing, eg. 1.3, or 2.0).</p>
@@ -1359,14 +1373,13 @@ A.B with the version you're preparing, e
</ul>
-</div> <!-- release-branches -->
-
+</div> <!-- creating-branch -->
-<div class="h2" id="porting-changes">
-<h2>Porting changes to release branches
+<div class="h3" id="porting-changes">
+<h3>Porting changes to a release branch
<a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#porting-changes"
title="Link to this section">¶</a>
-</h2>
+</h3>
<p>Once a release branch has been created, no development <i>ever</i>
takes place there. The only changes permitted are ones made to
@@ -1382,6 +1395,8 @@ release stabilization section</a>.</p>
</div> <!-- porting-changes -->
+</div> <!-- release-branches -->
+
<div class="h2" id="the-changes-file">
<h2>Managing the CHANGES file
Modified: subversion/site/publish/docs/community-guide/releasing.toc.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.toc.html?rev=1840822&r1=1840821&r2=1840822&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.toc.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.toc.html Thu Sep 13 14:06:20 2018
@@ -17,7 +17,11 @@
<li><a href="#releasing-release">The actual releasing</a></li>
</ul>
<li><a href="#release-branches">Creating and maintaining release branches</a></li>
-<li><a href="#porting-changes">Porting changes to release branches</a></li>
+ <ul>
+ <li><a href="#before-branching">Preparing to create a new minor release branch</a></li>
+ <li><a href="#creating-branch">Creating a new minor release branch</a></li>
+ <li><a href="#porting-changes">Porting changes to a release branch</a></li>
+ </ul>
<li><a href="#the-changes-file">Managing the CHANGES file</a></li>
<ul>
<li><a href="#writing-initial-changes">Writing the initial content for a branch</a></li>