svn commit: r797405 - /websites/staging/aries/trunk/content/overview/boardreports/october-2011.html

[bu...@apache.org]

Author: buildbot
Date: Mon Oct 24 15:41:11 2011
New Revision: 797405

Log:
Staging update by buildbot

Modified:
    websites/staging/aries/trunk/content/overview/boardreports/october-2011.html

Modified: websites/staging/aries/trunk/content/overview/boardreports/october-2011.html
==============================================================================
--- websites/staging/aries/trunk/content/overview/boardreports/october-2011.html (original)
+++ websites/staging/aries/trunk/content/overview/boardreports/october-2011.html Mon Oct 24 15:41:11 2011
@@ -250,28 +250,29 @@
           </td>
           <td height="100%" width="100%">
             <!-- Content -->
-            <div class="wiki-content"><h1 id="july_2011_board_report">July 2011 Board report</h1>
+            <div class="wiki-content"><h1 id="october_2011_board_report">October 2011 Board report</h1>
 <p>Apache Aries delivers a set of pluggable Java components enabling an enterprise OSGi application programming model.</p>
-<p>Users have asked for a release of the Aries JPA bundles and hence the snapshot bundles it depends on (Aries Util) - in particular due to:</p>
+<p>A new module called versionsing has been created for a utility to byte code analyse latest binaries with the last release of those binaries to find changes that should cause an OSGi Export-Package version attribute change, according to the OSGi Semantic Versioning whitepaper.</p>
+<p>Releases
+-
+Bug fix releases:</p>
 <ul>
-<li>the new 'runtime enhancer' that will mean entities can be enhanced as they are used in the runtime, rather than at development time.</li>
-<li>the support for EclipseLink (in addition to Apache OpenJPA) as a JPA provider</li>
+<li>Apache Aries Application 0.2.2</li>
+<li>Apache Aries Util 0.2.1</li>
 </ul>
-<p>The release process has just started. This will exercise our per bundle release process adhering to the OSGi Alliance Semantic Versioning recommendations.</p>
-<p>There have also been enhancements to the Aries JMX (whiteboard pattern) and Aries Subsystem (to use OSGi Core 4.3).</p>
-<p>Apache Geronimo, which consumes Apache Aries to implement its enterprise OSGi application programming model, has been readying a release. The performance enhancements in the Aries Proxy module which now makes use of the new Weaving Hooks OSGi specification, has had a few teething problems for Geronimo. All known problems are now resolved.</p>
+<p>We have been putting together a functional release from trunk but it's taking longer than we'd hoped. Due to our objective of getting the OSGi versioning correct, we're having to release more modules and correct more OSGi version ranges than we had hoped. A fully staged release of Apache Aries Blueprint and its dependencies is imminent.</p>
 <h2 id="project_branding_board_report_checklist">Project Branding Board Report Checklist</h2>
-<p>We've been reminded of this work and are reporting this checklist for the first time. We appreciate we're a bit behind the curve here, and are doing our best to catch up.</p>
+<p>A little progress here. Unfortunately there's been little progress here.</p>
 <ul>
 <li>Project Website Basics : homepage is aries.apache.org (done)</li>
 <li>Project Naming And Descriptions : use proper Apache forms, describe product, etc. (pending)</li>
 <li>Website Navigation Links : navbar links included, link to www.apache.org included (pending - feather link done)</li>
 <li>Trademark Attributions : attribution for all ASF marks included in footers, etc. (pending)</li>
 <li>Logos and Graphics : include TM, use consistent product logo on your site (pending)</li>
-<li>Project Metadata : DOAP file checkedin and up to date (pending - some minor updates needed)</li>
+<li>Project Metadata : DOAP file checkedin and up to date (done)</li>
 </ul>
 <h2 id="community_update">Community update</h2>
-<p>Roughly same number of dev@ subscribers at 119, user@ 148 subscribers up 14 since last report. John Ross was voted in as a committer after his significant work to the 'subsystem' module.</p>
+<p>No new committers since the last report.</p>
 <p>There are no board level issues.</p></div>
             <!-- Content -->
           </td>