You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2013/01/16 15:43:02 UTC
svn commit: r846848 - in /websites/staging/xmlgraphics/trunk/content: ./
fop/dev/release.html
Author: buildbot
Date: Wed Jan 16 14:43:02 2013
New Revision: 846848
Log:
Staging update by buildbot for xmlgraphics
Modified:
websites/staging/xmlgraphics/trunk/content/ (props changed)
websites/staging/xmlgraphics/trunk/content/fop/dev/release.html
Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 16 14:43:02 2013
@@ -1 +1 @@
-1433876
+1433955
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/release.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/release.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/release.html Wed Jan 16 14:43:02 2013
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
- <title>Apache(tm) FOP Development: Release Mechanics</title>
+ <title>Apache(tm) FOP Development: Release Process</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
@@ -342,7 +342,7 @@ $(document).ready(function () {
<div id="bannertext" style="border-bottom: 2px dashed #666666; height: 70px;">
<a href="/fop/"><img src="/images/apache-fop-logo.jpg" alt="The Apache FOP Project" width="120" height="65" style="float:left; margin-right: 15px;" /></a>
<h2>The Apache™ FOP Project</h2>
- </div><!-- <h1>Apache(tm) FOP Development: Release Mechanics</h1> -->
+ </div><!-- <h1>Apache(tm) FOP Development: Release Process</h1> -->
@@ -350,11 +350,11 @@ $(document).ready(function () {
<div id="items">
</div>
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a></div> -->
- <div class="section-content"><h1 id="apachewzxhzdk0-fop-development-release-mechanics">Apache™ FOP Development: Release Mechanics</h1>
+ <div class="section-content"><h1 id="apachewzxhzdk0-fop-development-release-process">Apache™ FOP Development: Release Process</h1>
<h2 id="intro">Introduction</h2>
<p>This page documents the process of creating a Apache™ FOP release. FOP releases are coordinated by some designated member of the team. The purpose of documenting it here is to facilitate consistency, ensure that the process is captured, and to allow others to comment on the process.</p>
<p>The checklist below is based on a combination of input from from Christian Geisert and Simon Pepping.</p>
-<h2 id="checklist">Checklist</h2>
+<h2 id="define">1. Define the new release</h2>
<ul>
<li>
<p>Determine which open bugs must be solved before a release can take place (release critical bugs). Make this bug depend on each release critical bug and write a short argument why the bug is release critical.</p>
@@ -368,6 +368,9 @@ $(document).ready(function () {
<li>
<p>Commit any outstanding changes</p>
</li>
+</ul>
+<h2 id="prepare">2. Prepare the new release</h2>
+<ul>
<li>
<p>Create a branch called <code>branches/fop-v_vv</code></p>
</li>
@@ -407,6 +410,9 @@ $(document).ready(function () {
<li>
<p>Create signatures. Don't forget to upload your KEY: <code>gpg -a -b --force-v3-sigs fop-1.0-src.tar.gz</code> etc.</p>
</li>
+</ul>
+<h2 id="publish">3. Publish the new release</h2>
+<ul>
<li>
<p>Upload the dist and signature files to your web directory on people.apache.org (An account on minotaur is needed): <code>scp fop-1.0*.tar.gz* chrisg@people.apache.org:public_html/</code></p>
</li>
@@ -419,6 +425,9 @@ $(document).ready(function () {
<li>
<p>Make a test download.</p>
</li>
+</ul>
+<h2 id="vote">4. Vote for the new release</h2>
+<ul>
<li>
<p>Start a vote for the release on <code>general@xmlgraphics.apache.org</code>. The message should point to the release files and list the MD5 sums (<code>cat *.md5</code>). The vote should remain open for 72hrs.</p>
</li>
@@ -431,9 +440,14 @@ $(document).ready(function () {
<li>
<p>Wait 24 hours (for the mirrors to catch up).</p>
</li>
-<li>
-<p>Merge the changes of the subversion release branch back into trunk (not the version number in the build file) and delete the branch.</p>
-</li>
+</ul>
+<h2 id="update">5. Update material</h2>
+<h3 id="svn">5.1 Subversion</h3>
+<ul>
+<li>Merge the changes of the subversion release branch back into trunk (not the version number in the build file) and delete the branch.</li>
+</ul>
+<h3 id="jira">5.2 Jira</h3>
+<ul>
<li>
<p>Ask an FOP Jira admin to</p>
<ul>
@@ -445,17 +459,20 @@ $(document).ready(function () {
<li>create an issue at <a href="https://issues.apache.org/jira/browse/INFRA">Jira-INFRA</a>.</li>
</ul>
</li>
+</ul>
+<h3 id="cms">5.3 CMS</h3>
+<ul>
<li>
-<p>In CMS doc, copy trunk directory to a new release directory with the new version number.</p>
+<p>Copy trunk directory to a new release directory with the new version number.</p>
</li>
<li>
-<p>In CMS doc, copy following files to the new release directory:</p>
+<p>Copy following files to the new release directory:</p>
<ul>
<li><code>known-issues.mdtext</code> as <code>knownissues-overview.mdtext</code></li>
</ul>
</li>
<li>
-<p>In CMS doc, update all markdown linkIds to the new release (elementids are of the form <code>[linkId]: fop_version/path_to_page_XXX"</code> at the beginning of the files):</p>
+<p>Update all markdown linkIds to the new release (elementids are of the form <code>[linkId]: fop_version/path_to_page_XXX"</code> at the beginning of the files):</p>
<ul>
<li><code>faq.mdtext</code></li>
<li><code>fo.mdtext</code></li>
@@ -465,7 +482,7 @@ $(document).ready(function () {
</ul>
</li>
<li>
-<p>In CMS doc, update the following files to the new release</p>
+<p>Update the following files to the new release</p>
<ul>
<li><code>fop-sidenav.mdtext</code></li>
<li><code>download.mdtext</code></li>
@@ -474,7 +491,7 @@ $(document).ready(function () {
</ul>
</li>
<li>
-<p>In CMS doc, in the new release directory, update the following files:</p>
+<p>In the new release directory, update the following files:</p>
<ul>
<li><code>index.mdtext</code></li>
<li><code>compiling.mdtext</code> (change the introduction for trunk to that for a release).</li>
@@ -484,14 +501,29 @@ $(document).ready(function () {
<li>
<p>Publish the updated documentation to the FOP website.</p>
</li>
-<li>
-<p>Post announcements on <code>fop-dev</code> and <code>fop-user</code> and other related mailing lists.</p>
-</li>
-<li>
-<p>Deploy the maven bundle.</p>
-</li>
</ul>
-<h2 id="other-checklists">Resources</h2>
+<h3 id="maven">5.3 Maven</h3>
+<ul>
+<li>Deploy the maven bundle.</li>
+</ul>
+<h2 id="announce">6 Announce the new release</h2>
+<p>Post announcements on following suggested lists:</p>
+<ul>
+<li>fop-dev@xmlgraphics.apache.org</li>
+<li>fop-users@xmlgraphics.apache.org</li>
+<li>general@xmlgraphics.apache.org</li>
+<li>general@xml.apache.org</li>
+<li>announce@apache.org (from your apache.org address)</li>
+<li>xsl-list@lists.mulberrytech.com (subscriber-only)</li>
+<li>xsl-fo@yahoogroups.com (subscriber-only)</li>
+<li>www-xsl-fo@w3.org</li>
+<li>docbook-apps@lists.oasis-open.org (subscriber-only)</li>
+<li>dita-users@yahoogroups.com (subscriber-only) (http://dita-ot.sourceforge.net/)</li>
+<li>http://xslfo-zone.com/news/index.jsp</li>
+<li>http://www.w3.org/Style/XSL/</li>
+<li>http://freshmeat.net/projects/fop/</li>
+</ul>
+<h2 id="resources">Resources</h2>
<p>The following is a sample of some other project release checklists, which might be consulted for ideas:</p>
<ul>
<li>
@@ -512,49 +544,6 @@ $(document).ready(function () {
<li>
<p>Stefan Bodewig's <a href="http://people.apache.org/~bodewig/mirror.html">Making your Downloads Mirrorable</a></p>
</li>
-</ul>
-<h2 id="announcements">Announcing the release</h2>
-<p>Here's a suggested list of places where to announce new FOP releases:</p>
-<ul>
-<li>
-<p>fop-dev@xmlgraphics.apache.org</p>
-</li>
-<li>
-<p>fop-users@xmlgraphics.apache.org</p>
-</li>
-<li>
-<p>general@xmlgraphics.apache.org</p>
-</li>
-<li>
-<p>general@xml.apache.org</p>
-</li>
-<li>
-<p>announce@apache.org (from your apache.org address)</p>
-</li>
-<li>
-<p>xsl-list@lists.mulberrytech.com (subscriber-only)</p>
-</li>
-<li>
-<p>xsl-fo@yahoogroups.com (subscriber-only)</p>
-</li>
-<li>
-<p>www-xsl-fo@w3.org</p>
-</li>
-<li>
-<p>docbook-apps@lists.oasis-open.org (subscriber-only)</p>
-</li>
-<li>
-<p>dita-users@yahoogroups.com (subscriber-only) (http://dita-ot.sourceforge.net/)</p>
-</li>
-<li>
-<p>http://xslfo-zone.com/news/index.jsp</p>
-</li>
-<li>
-<p>http://www.w3.org/Style/XSL/</p>
-</li>
-<li>
-<p>http://freshmeat.net/projects/fop/</p>
-</li>
</ul></div>
</div>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org