incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1777806 [1/2] - in /incubator/public/trunk/content: facilities.xml guides/draft-simple-release-management.xml guides/release-java.xml guides/release.xml guides/release_manifest.txt guides/releasemanagement.xml
Date Sat, 07 Jan 2017 15:25:01 GMT
Author: johndament
Date: Sat Jan  7 15:25:01 2017
New Revision: 1777806

Clean up the release management policy and guide to better rely on foundation wide policies,
reducing duplication.
Updated the facilities guide for URL generation issues.


Modified: incubator/public/trunk/content/facilities.xml
--- incubator/public/trunk/content/facilities.xml [utf-8] (original)
+++ incubator/public/trunk/content/facilities.xml [utf-8] Sat Jan  7 15:25:01 2017
@@ -48,7 +48,7 @@
         First the metadata. Each project needs to maintain their entry in the
         content/podlings.xml file in SVN
-        (see <a href="guides/mentor.html#Overview">notes</a>).
+        (see <a href="&root-path;/guides/mentor.html#Overview">notes</a>).
         The following facilities rely on that being up-to-date.
         Please be a self-sufficient project from the very beginning.
         Do not wait for your Mentors - it is up to you.
@@ -57,7 +57,7 @@
         Add the entry for your project as soon as possible after the Acceptance
         phase is complete. Keep it up-to-date throughout your incubation
         (e.g. mentor changes) and during the
-        <a href="/guides/graduation.html#unincubate">graduation</a> phases.
+        <a href="&root-path;/guides/graduation.html#unincubate">graduation</a>
     <section id="publish">
@@ -66,18 +66,18 @@
         When changes are committed to the podlings.xml summary file,
         then the CMS is triggered and generates the following facilities.
         Please follow through to publish the changes.
-        See <a href="/guides/website.html">notes</a>.
+        See <a href="&root-path;/guides/website.html">notes</a>.
     <section id="current-podlings">
       <title>Overview list of current podlings</title>
-        The "<a href="/projects/#current">Currently in incubation</a>" table.
+        The "<a href="&root-path;/projects/#current">Currently in incubation</a>"
         Shows Description, Champion, Mentors, and Start date.
         Note that each project can be directly referenced, e.g.
-        <a href="/projects/#allura"></a>
+        <a href="&root-path;/projects/#allura"></a>
         Generated by CMS from podlings.xml using content/stylesheets/project-index.xsl file.
@@ -90,7 +90,7 @@
     <section id="report-schedule">
       <title>Monthly Reporting Schedule</title>
-        <a href="/report-groups.txt"></a>
+        <a href="&root-path;/report-groups.txt"></a>
         Generated by CMS from podlings.xml using report-groups.xsl file.
@@ -100,7 +100,7 @@
     <section id="report-next-month">
       <title>Reporting next month</title>
-        <a href="/report-next-month.html"></a>
+        <a href="&root-path;/report-next-month.html"></a>
         Generated by CMS from podlings.xml using report-next-month.xsl file.
@@ -130,7 +130,7 @@
         Anyone can be a shepherd. Please add and maintain your entry in the
-        content/shepherds.json file in SVN.
+        <em>content/shepherds.json</em> file in SVN.
         The script uses that data around the beginning of
@@ -141,19 +141,19 @@
     <section id="clutch">
       <title>Status of the Clutch</title>
-        The <a href="/clutch.html">Clutch</a> table shows the status of
+        The <a href="&root-path;/clutch.html">Clutch</a> table shows the
status of
         various aspects of incubation for each current project.
-        It also <a href="/clutch.html#steps">explains</a> each step
+        It also <a href="&root-path;/clutch.html#steps">explains</a> each
         and links to some relevant documentation.
         Note that each project row can be directly referenced, e.g.
-        <a href="/clutch.html#allura"></a>
+        <a href="&root-path;/clutch.html#allura"></a>
         Clutch uses podlings.xml and each project status page and other resources.
         Run this manually from the top of SVN.
-        See operational <a href="/clutch.html#notes">notes</a> and other notes
+        See operational <a href="&root-path;/clutch.html#notes">notes</a>
and other notes in
         These are some of the resources that are consulted:
@@ -201,20 +201,22 @@
         otherwise you will keep getting reminders.
-        There are three groups:<br/>
-        group-1=Jan,Apr,Jul,Oct group-2=Feb,May,Aug,Nov group-3=Mar,Jun,Sep,Dec
+        There are three groups: <br/>
+        group-1=Jan,Apr,Jul,Oct <br/>
+        group-2=Feb,May,Aug,Nov <br/>
+        group-3=Mar,Jun,Sep,Dec <br/>
         The reminder robot uses the lists of report_due_*.txt files, being the
         dev mail list addresses of the set of projects that are due to report.
         Gathered, validated, and output by Clutch.
-        See <a href="/clutch.html#data">data files</a> and
-        <a href="/clutch.html#notes">notes</a>.
+        See <a href="&root-path;/clutch.html#data">data files</a> and
+        <a href="&root-path;/clutch.html#notes">notes</a>.
         See the
-        "<a href="">board_reminders</a>"
-        code in infrastructure SVN.
+        <a href=""></a>
+        code in SVN.
         Note: Eventually it would be good to extract the handling of these
@@ -235,7 +237,7 @@
     <section id="history">
       <title>Incubator history</title>
-        <a href="/history/"></a>
+        <a href="&root-path;/history/"></a>
         Generated by CMS from podlings.xml using current.xsl file and entry.xsl file.

Modified: incubator/public/trunk/content/guides/release-java.xml
--- incubator/public/trunk/content/guides/release-java.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/release-java.xml [utf-8] Sat Jan  7 15:25:01 2017
@@ -28,44 +28,11 @@ limitations under the License.
           <section id='TOC'><title>Contents</title><toc/></section>
-    <section id='release-distribution'><title>Distributing Releases</title>
           Stop ignoring the elephant
-        <section id='distributing-eclipse'><title>Eclipse Update Site</title>
-          <p>
-          Podlings may distribute suitable artifacts through an 
-          <a href=''>Eclipse</a> update site.
-          All artifacts distributed through the update site must satisfy the standard
-          <a href='#distribution-policy-overview'>policy</a>. This implies that:
-          </p>
-          <ul>
-            <li>The update site must be contained within the  
-            <a href='#glossary-podling-dist'>podling distribution directory</a>.</li>
-            <li>All artifacts must be 
-            <a href=''>signed
and summed</a>.</li>
-            <li><a href='#distribution-mirroring'>Mirroring</a> must be
-          </ul>
-          <p>Detailed instructions on how to setup an Incubator Project to have an

-            <a href='releasing-eclipse-update-site.html'>Eclipse update site with Mirroring</a>
are available.</p>
-          <!--  
-          <p>
-          Mirroring an update site requires some additional effort. The <code>mirrorsURL</code>
-          of the root <code>site</code> element in the <code>site.xml</code>
should be set the URL
-          of a mirroring script. For example
-          </p>
-          <source>
-          &lt;site mirrorsURL="{podling}-eclipse-update-
-            &lt;description&gt;Apache {Podling} Eclipse Update Site&lt;/description&gt;
-            ...
-          &lt;/site&gt;
-          </source>
-          -->
-        </section>
-    </section> 
     <section id='release-guidelines'><title>Release Guidelines</title>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message