Return-Path: 
 <commits-return-2925-apmail-aries-commits-archive=aries.apache.org@aries.apache.org>
Delivered-To: apmail-aries-commits-archive@www.apache.org
Received: (qmail 95569 invoked from network); 9 Feb 2011 14:46:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 9 Feb 2011 14:46:44 -0000
Received: (qmail 51787 invoked by uid 500); 9 Feb 2011 14:46:44 -0000
Delivered-To: apmail-aries-commits-archive@aries.apache.org
Received: (qmail 51735 invoked by uid 500); 9 Feb 2011 14:46:43 -0000
Mailing-List: contact commits-help@aries.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@aries.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@aries.apache.org>
List-Post: <mailto:commits@aries.apache.org>
List-Id: <commits.aries.apache.org>
Reply-To: dev@aries.apache.org
Delivered-To: mailing list commits@aries.apache.org
Received: (qmail 51724 invoked by uid 99); 9 Feb 2011 14:46:42 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Feb 2011 14:46:42 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Feb 2011 14:46:41 +0000
Received: by eris.apache.org (Postfix, from userid 65534)
	id D10CC23889BB; Wed,  9 Feb 2011 14:46:21 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r785074 -
 /websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html
Date: Wed, 09 Feb 2011 14:46:21 -0000
To: commits@aries.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20110209144621.D10CC23889BB@eris.apache.org>

Author: buildbot
Date: Wed Feb  9 14:46:21 2011
New Revision: 785074

Log:
Staging update by buildbot

Modified:
    websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html

Modified: websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html
==============================================================================
--- websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html (original)
+++ websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html Wed Feb  9 14:46:21 2011
@@ -236,7 +236,7 @@
             <!-- Content -->
             <div class="wiki-content"><h1 id="release_process_requirements">Release process requirements</h1>
 <p>Up to release 0.3 of Aries we released all of the modules at once, along with a set of samples which demonstrated how the Aries components could be used together.</p>
-<p>After release 0.3 we wanted to rexamine the release process, the priimary motivation for this was the observation that our 
+<p>After release 0.3 we wanted to rexamine the release process, the primary motivation for this was the observation that our 
 current process did not use semantic versioning, and, as an OSGi project we should be demonstrating best OSGi practice.</p>
 
 <p>We started with the following set of requirements for any Aries release: </p>
@@ -246,9 +246,9 @@ current process did not use semantic ver
 <tr><td class="confluenceTd">  1 </td><td class="confluenceTd"> Follows OSGi semantic versioning</td><td class="confluenceTd"> No </td></tr>
 <tr><td class="confluenceTd">  2 </td><td class="confluenceTd"> Must have a buildable source distribution </td><td class="confluenceTd"> Yes </td></tr>
 <tr><td class="confluenceTd">  3 </td><td class="confluenceTd"> Must have release notes</td><td class="confluenceTd"> Yes </td></tr>
-<tr><td class="confluenceTd">  4 </td><td class="confluenceTd"> Must be publicly announced </td><td class="confluenceTd">  </td></tr>
+<tr><td class="confluenceTd">  4 </td><td class="confluenceTd"> Must be publicly announced </td><td class="confluenceTd"> Yes </td></tr>
 <tr><td class="confluenceTd">  5 </td><td class="confluenceTd"> An easy way for users to download the bundles for a given component</td><td class="confluenceTd"> Yes </td></tr>
-<tr><td class="confluenceTd">  6 </td><td class="confluenceTd"> Easy tagging/branching mechanism</td><td class="confluenceTd"> ? </td></tr>
+<tr><td class="confluenceTd">  6 </td><td class="confluenceTd"> Easy tagging/branching mechanism</td><td class="confluenceTd"> Yes </td></tr>
 <tr><td class="confluenceTd">  7 </td><td class="confluenceTd"> A way to provide bug fixes</td><td class="confluenceTd"> Yes  </td></tr>
 <tr><td class="confluenceTd">  8 </td><td class="confluenceTd"> A way to ensure that a given component doesn't have conflicting dependencies </td><td class="confluenceTd"> ?  </td></tr>
 </table>