incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Trieloff <>
Subject Re: January 2007 Incubator Report (Revised)
Date Mon, 22 Jan 2007 19:13:10 GMT
Noel J. Bergman wrote:
> Carl Trieloff wrote:
>> We created a report for Qpid. I guess that we mailed it to the wrong
>> location, where should the report be sent for inclusion?
> The Wiki is the staging area for the report, or you can post to general@.
> Where did you send it?
> 	--- Noel


Here is the mail, Should sent it for us and should be able to tell you 
where he sent it.


---- snip from our list ----

Hello fellow PPMC memebers,
I have put together a report with some help from Carl that I present
here for your comments and suggestions. I would like to submit this
report on Friday so if you can get your comments to me by then I will
integrate them and post the results.


January Incubator Report for Apache 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 is up-to-date.

* Any legal, cross-project or personal issues that still need to be

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).
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 
We will also be pushing forward official JMS compliance certification
for both brokers.
Would like to create a release of the full code set

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message