svn commit: r785325 - in /websites/production/aries: ./ content/development/ReleaseProcessRequirements.html content/overview/boardreports/february-2011.html

[hu...@apache.org]

Author: hughesj
Date: Fri Feb 11 23:47:46 2011
New Revision: 785325

Log:
Publishing merge to aries site by hughesj

Modified:
    websites/production/aries/   (props changed)
    websites/production/aries/content/development/ReleaseProcessRequirements.html
    websites/production/aries/content/overview/boardreports/february-2011.html

Propchange: websites/production/aries/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Fri Feb 11 23:47:46 2011
@@ -1 +1 @@
-/websites/staging/aries/trunk:782169-785099
+/websites/staging/aries/trunk:782169-785324

Modified: websites/production/aries/content/development/ReleaseProcessRequirements.html
==============================================================================
--- websites/production/aries/content/development/ReleaseProcessRequirements.html (original)
+++ websites/production/aries/content/development/ReleaseProcessRequirements.html Fri Feb 11 23:47:46 2011
@@ -265,7 +265,7 @@ will need to get Util version 0.4 to go 
 <ol>
 <li>Not using of OSGi semantic versioning of bundles. After every we release we bump the major versions of all bundles in trunk.</li>
 </ol>
-<p>Package versions are managed separately (correctly) and the Maven bundle plugin will ensure packges are imported in the correct range based of
+<p>Package versions are managed separately (correctly) and the Maven bundle plugin will ensure packages are imported in the correct range based of
  the projects dependencies. Implementers need to use "provide:=true" to get the correct range. Package export version should be maintained 
 either using package.info or in the pom.xml.</p>
 <h2 id="releasing_by_module">Releasing by module</h2>
@@ -273,7 +273,7 @@ either using package.info or in the pom.
 really just an evolution of the process that we already use but it would involve 
 using semantic versioning of bundles. One might visualise the process like this: </p></p>
 <p><img alt="rel" src="release_by_module.png" /></p>
-<p>In this case, we have a module version (independent of the version of its sub-modules) and a set of sub-modules which may each be indepndently versioned.</p>
+<p>In this case, we have a module version (independent of the version of its sub-modules) and a set of sub-modules which may each be independently versioned.</p>
 
 <h3 id="advantages_of_release_by_module">Advantages of release by module</h3>
 <ol>

Modified: websites/production/aries/content/overview/boardreports/february-2011.html
==============================================================================
--- websites/production/aries/content/overview/boardreports/february-2011.html (original)
+++ websites/production/aries/content/overview/boardreports/february-2011.html Fri Feb 11 23:47:46 2011
@@ -236,8 +236,9 @@
             <!-- Content -->
             <div class="wiki-content"><h1 id="february_2011_board_report">February 2011 Board report</h1>
 <p>Aries delivers a set of pluggable Java components enabling an enterprise OSGi application programming model.</p>
-<p>Aries 0.3 has now been released. Aries Application 0.2.1 is being released to assist Geronimo. Now that the first full Aries release since graduation has happened, and that there is a desire to consider OSGi semantic versioning guidelines we are discussing whether releasing at a finer grained level is more appropriate.</p>
-<p>Community update: dev@ 117 subscribers (-1), user@ 129 subscribers (+2). The dev@ list continues to be active with less traffic on the user@ list. No new committers or PMC members since the January report.</p>
+<p>Aries 0.3 has now been released. Aries Application 0.2.1 is being released to assist Geronimo. This is the first time Aries has released a single module.</p>
+<p>Now that the first full Aries release since graduation has happened, and that there is a desire to consider OSGi semantic versioning guidelines we are discussing whether releasing at a finer grained level is more appropriate. There is much good discussion about what makes sense for Aries, with input from what happens in Felix, Sling and ACE.</p>
+<p>Community update: largely unchanged since last month dev@ 117 subscribers, user@ 127 subscribers. The dev@ list continues to be active with less traffic on the user@ list. No new committers or PMC members since the January report.</p>
 <p>There are no board level issues.</p></div>
             <!-- Content -->
           </td>