incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "January2007" by MartinRitchie
Date Wed, 17 Jan 2007 12:08:05 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by MartinRitchie:

The comment on the change is:
Added Qpid Status report

  The following projects still need to add a section below:
   * Ivy
   * JuiCE
-  * Qpid
   * Roller
  Remove yourself from the above list once you add your report.
@@ -174, +173 @@

+ === Qpid ===
+ The Apache Qpid Project provides an open and interoperable, multiple
+ language implementations of the Advanced Messaged Queuing Protocol
+ (AMQP) specification
+ Date of entry to the Incubator : 2006-09
+ Top three items to resolve before graduation
+  1. Defining a policy for adding new committers
+  2. Understanding the details between JCP and announce compliance
+  3. Making sure we are comfortable with the working relationship between Qpid and the AMQP
Working Group.
+ Our STATUS file needs to be updated wrt this report which will be done in the comming weeks
as we add our first group of new committers.
+ * Any legal, cross-project or personal issues that still need to be
+ addressed?
+ The whole project has not gone through release review and the license files and notices
need to be checked for all languages and components.
+ * Latest developments.
+  * Since entering into incubation we have had one release of the java code base (M1). 
+  * We have migrated our build system from ant to maven.
+  * Development has been moving forward. with improvements in memory footprint management
passing the JMS TCK in with the java broker.
+  * Addition of .NET client
+  * Contributions from 5+ non committers
+  * The creation of the first draft of Web site
+  * General progress on all models in the code base
+ * Plans and expectations for the next period?
+ During the next period we plan on improving the stability of all language variants. 
+ Working towards a standard interoperability test suite and improved test code coverage of
the whole code base.
+ To this end we would like to get all the languages passing each others tests.
+ We will also be pushing forward official JMS compliance certification for both brokers.
+ Would like to create a release of the full code set.
+ ----

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message