aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1466568 - /aries/site/trunk/content/overview/boardreports/april-2013.mdtext
Date Wed, 10 Apr 2013 17:03:40 GMT
Author: hughesj
Date: Wed Apr 10 17:03:39 2013
New Revision: 1466568

April 2013 board report content

      - copied, changed from r1465520, aries/site/trunk/content/overview/boardreports/january-2013.mdtext

Copied: aries/site/trunk/content/overview/boardreports/april-2013.mdtext (from r1465520, aries/site/trunk/content/overview/boardreports/january-2013.mdtext)
--- aries/site/trunk/content/overview/boardreports/january-2013.mdtext (original)
+++ aries/site/trunk/content/overview/boardreports/april-2013.mdtext Wed Apr 10 17:03:39 2013
@@ -16,43 +16,43 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
-# January 2013 Board report
+# April 2013 Board report
 Apache Aries delivers a set of pluggable Java components enabling an enterprise OSGi application
programming model.
-##Project update
+## Releases
+* Apache Aries Subsystem 1.0.0
+> This is the reference implementation of the OSGi Subsystem Service Specification which
"provides a declarative model for defining resource collections, including bundles, and
+an API for installing and managing those collections of resources." See OSGi Enterprise Release
5 specification chapter 134.
+subsystem-api, subsystem-core, and subsystem-obr 1.0.0 were released. 
+* Apache Aries SPI-Fly 1.0.0
+> This is the reference implementation of the OSGi Service Loader Mediator Specification
which "defines a mediator that ensures that the Java SE 6 Service Loader is useful in an OSGi
+Framework, allowing programs that leverage the Service Loader to be used in OSGi frameworks
+almost as-is." See OSGi Enterprise Release 5 specification chapter 133.
+All the spi-fly bundles were released.
+* Apache Aries Blueprint no-OSGi 1.0.0
+>Provides the ability to use Blueprint Schema, xml and injection outside of the OSGi environment.
-* The SPI Fly component now fully implements the ServiceLoader Mediator
-Specification 1.0 from the OSGi Enterprise R5 spec (chapter 133). It is the
-Reference Implementation of this spec and passes all the OSGi TCK tests for
-* The JMX component in Aries now fully implements OSGi/JMX 1.1 from the
-OSGi Enterprise R5 spec (chapter 124). As of this version it is the
-Reference Implementation of this spec and passes all the OSGi TCK tests for
-    Both components are available in SNAPSHOT versions in the Aries code base.
-They are waiting to be released.
-* The Semantic Versioning maven plugin component is now being used in our own builds - for
modules that have 1.0 or
-above releases. For those modules, the bytecode output to the target directory will be checked
for semantic changes
-since the last release. If the semantic version is incorrect, the build 
-will fail.
-* Apache Karaf 2.3.0 - one of our significant consumers - has moved up to include Apache
Aries 1.0.0 releases.
-No releases this quarter.
-##Project Branding Board Report Checklist 
-* Project Website Basics : homepage is (done)
-* Project Naming And Descriptions : use proper Apache forms, describe product, etc. (pending)
-* Website Navigation Links : navbar links included, link to included (pending
- feather link done)
-* Trademark Attributions : attribution for all ASF marks included in footers, etc. (pending)
-* Logos and Graphics : include TM, use consistent product logo on your site (pending)
-* Project Metadata : DOAP file checkedin and up to date (done)
+* Apache Aries Blueprint Web 1.0.0
+>Provides a web context listener to bootstrap the no-OSGi Blueprint container inside a
+* Apache Aries JMX 1.1.0 & 1.1.1
+>This implements the OSGi JMX Management Model Specification and has been updated to V1.1
of that spec (which requires V1.2 of JMX).
+* Apache Aries Semantic Versioning Checker 0.1.0
+>This compares the bytecode of a module's previous release, with that being built to determine
whether the package and bundle versions are semantically versioned correctly.
+##Project update
-##Community update
-No new committers since the last report. The user/dev lists and JIRAs have had some varied
discussions across the Aries modules.
+No new committers since the last report. Contributions are coming through on the dev list
through git pull requests and patches to JIRAs and we continue to have varied discussions
across the variety of our sub components. 
 There are no board level issues.
\ No newline at end of file

View raw message