You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by jo...@apache.org on 2017/01/07 15:25:01 UTC
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
Author: johndament
Date: Sat Jan 7 15:25:01 2017
New Revision: 1777806
URL: http://svn.apache.org/viewvc?rev=1777806&view=rev
Log:
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.
Removed:
incubator/public/trunk/content/guides/draft-simple-release-management.xml
incubator/public/trunk/content/guides/release.xml
incubator/public/trunk/content/guides/release_manifest.txt
Modified:
incubator/public/trunk/content/facilities.xml
incubator/public/trunk/content/guides/release-java.xml
incubator/public/trunk/content/guides/releasemanagement.xml
Modified: incubator/public/trunk/content/facilities.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/facilities.xml?rev=1777806&r1=1777805&r2=1777806&view=diff
==============================================================================
--- 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 @@
<p>
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> phases.
</p>
</section>
<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>.
</p>
</section>
<section id="current-podlings">
<title>Overview list of current podlings</title>
<p>
- The "<a href="/projects/#current">Currently in incubation</a>" table.
+ The "<a href="&root-path;/projects/#current">Currently in incubation</a>" table.
Shows Description, Champion, Mentors, and Start date.
</p>
<p>
Note that each project can be directly referenced, e.g.
- <a href="/projects/#allura">http://incubator.apache.org/projects/#allura</a>
+ <a href="&root-path;/projects/#allura">http://incubator.apache.org/projects/#allura</a>
</p>
<p>
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>
<p>
- <a href="/report-groups.txt">http://incubator.apache.org/report-groups.txt</a>
+ <a href="&root-path;/report-groups.txt">http://incubator.apache.org/report-groups.txt</a>
</p>
<p>
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>
<p>
- <a href="/report-next-month.html">http://incubator.apache.org/report-next-month.html</a>
+ <a href="&root-path;/report-next-month.html">http://incubator.apache.org/report-next-month.html</a>
</p>
<p>
Generated by CMS from podlings.xml using report-next-month.xsl file.
@@ -130,7 +130,7 @@
</p>
<p>
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.
</p>
<p>
The script assign_shepherds.py uses that data around the beginning of
@@ -141,19 +141,19 @@
<section id="clutch">
<title>Status of the Clutch</title>
<p>
- 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 step
and links to some relevant documentation.
</p>
<p>
Note that each project row can be directly referenced, e.g.
- <a href="/clutch.html#allura">http://incubator.apache.org/clutch.html/#allura</a>
+ <a href="&root-path;/clutch.html#allura">http://incubator.apache.org/clutch.html/#allura</a>
</p>
<p>
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 in clutch.py
+ See operational <a href="&root-path;/clutch.html#notes">notes</a> and other notes in clutch.py
</p>
<p>
These are some of the resources that are consulted:
@@ -201,20 +201,22 @@
otherwise you will keep getting reminders.
</p>
<p>
- 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/>
</p>
<p>
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>.
</p>
<p>
See the
- "<a href="https://svn.apache.org/repos/infra/infrastructure/trunk/tools/board_reminders/">board_reminders</a>"
- code in infrastructure SVN.
+ <a href="https://svn.apache.org/repos/asf/incubator/public/trunk/report_reminders.py">report_reminders.py</a>
+ code in SVN.
</p>
<p>
Note: Eventually it would be good to extract the handling of these
@@ -235,7 +237,7 @@
<section id="history">
<title>Incubator history</title>
<p>
- <a href="/history/">http://incubator.apache.org/history/</a>
+ <a href="&root-path;/history/">http://incubator.apache.org/history/</a>
</p>
<p>
Generated by CMS from podlings.xml using current.xsl file and entry.xsl file.
Modified: incubator/public/trunk/content/guides/release-java.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/release-java.xml?rev=1777806&r1=1777805&r2=1777806&view=diff
==============================================================================
--- 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>
- <section id='release-distribution'><title>Distributing Releases</title>
<!--
TODO:
Maven:
Stop ignoring the elephant
-->
- <section id='distributing-eclipse'><title>Eclipse Update Site</title>
- <p>
- Podlings may distribute suitable artifacts through an
- <a href='http://www.eclipse.org'>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='http://www.apache.org/dev/release-signing.html#keys-policy'>signed and summed</a>.</li>
- <li><a href='#distribution-mirroring'>Mirroring</a> must be used.</li>
- </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> attribute
- 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>
- <site mirrorsURL="http://incubator.apache.org/mirrors-support/{podling}-eclipse-update- -xml.cgi">
- <description>Apache {Podling} Eclipse Update Site</description>
- ...
- </site>
- </source>
-
- -->
- </section>
- </section>
<section id='release-guidelines'><title>Release Guidelines</title>
<p>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org