incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1004372 [1/3] - in /websites/staging/incubator/trunk/content: ./ guides/
Date Sat, 07 Jan 2017 15:25:37 GMT
Author: buildbot
Date: Sat Jan  7 15:25:37 2017
New Revision: 1004372

Staging update by buildbot for incubator

    websites/staging/incubator/trunk/content/   (props changed)

Propchange: websites/staging/incubator/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Sat Jan  7 15:25:37 2017
@@ -1 +1 @@

Modified: websites/staging/incubator/trunk/content/facilities.html
--- websites/staging/incubator/trunk/content/facilities.html (original)
+++ websites/staging/incubator/trunk/content/facilities.html Sat Jan  7 15:25:37 2017
@@ -193,7 +193,7 @@ Others yet to be documented
         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="./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.
@@ -202,7 +202,7 @@ Others yet to be documented
         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="./guides/graduation.html#unincubate">graduation</a> phases.
         <h2 id='publish'><img src="./images/redarrow.gif" />Remember to publish
the generated results</h2>
@@ -211,18 +211,18 @@ Others yet to be documented
         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="./guides/website.html">notes</a>.
         <h2 id='current-podlings'><img src="./images/redarrow.gif" />Overview
list of current podlings</h2>
 <div class="section-content">
-        The "<a href="/projects/#current">Currently in incubation</a>" table.
+        The "<a href="./projects/#current">Currently in incubation</a>" table.
         Shows Description, Champion, Mentors, and Start date.
         Note that each project can be directly referenced, e.g.
-        <a href="/projects/#allura"></a>
+        <a href="./projects/#allura"></a>
         Generated by CMS from podlings.xml using content/stylesheets/project-index.xsl file.
@@ -235,7 +235,7 @@ Others yet to be documented
         <h2 id='report-schedule'><img src="./images/redarrow.gif" />Monthly Reporting
 <div class="section-content">
-        <a href="/report-groups.txt"></a>
+        <a href="./report-groups.txt"></a>
         Generated by CMS from podlings.xml using report-groups.xsl file.
@@ -245,7 +245,7 @@ Others yet to be documented
         <h2 id='report-next-month'><img src="./images/redarrow.gif" />Reporting
next month</h2>
 <div class="section-content">
-        <a href="/report-next-month.html"></a>
+        <a href="./report-next-month.html"></a>
         Generated by CMS from podlings.xml using report-next-month.xsl file.
@@ -275,7 +275,7 @@ Others yet to be documented
         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
@@ -286,19 +286,19 @@ Others yet to be documented
         <h2 id='clutch'><img src="./images/redarrow.gif" />Status of the Clutch</h2>
 <div class="section-content">
-        The <a href="/clutch.html">Clutch</a> table shows the status of
+        The <a href="./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="./clutch.html#steps">explains</a> each step
         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="./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="./clutch.html#notes">notes</a> and other notes
         These are some of the resources that are consulted:
@@ -346,20 +346,22 @@ Others yet to be documented
         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="./clutch.html#data">data files</a> and
+        <a href="./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
@@ -380,7 +382,7 @@ Others yet to be documented
         <h2 id='history'><img src="./images/redarrow.gif" />Incubator history</h2>
 <div class="section-content">
-        <a href="/history/"></a>
+        <a href="./history/"></a>
         Generated by CMS from podlings.xml using current.xsl file and entry.xsl file.

Modified: websites/staging/incubator/trunk/content/guides/release-java.html
--- websites/staging/incubator/trunk/content/guides/release-java.html (original)
+++ websites/staging/incubator/trunk/content/guides/release-java.html Sat Jan  7 15:25:37
@@ -121,16 +121,6 @@ Contents
-<li><a href='#release-distribution'>
-Distributing Releases
- </a>
- <ul>
-<li><a href='#distributing-eclipse'>
-Eclipse Update Site
- </a>
 <li><a href='#release-guidelines'>
 Release Guidelines
@@ -230,27 +220,6 @@ Jar MANIFEST
-        <h2 id='release-distribution'><img src="../images/redarrow.gif" />Distributing
-<div class="section-content">
-<h3 id='distributing-eclipse'>Eclipse Update Site</h3>
-<div class="section-content">
-          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>
-            <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>
         <h2 id='release-guidelines'><img src="../images/redarrow.gif" />Release
 <div class="section-content">

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

View raw message