I think it might be time to start becoming more concrete on the M3
release. So far a few people have edited this
for M3: http://cwiki.apache.org/qpid/roadmap.html
I have updated with what we have done so far, and a good part is
completed. Can we hash out on this thread and
get M3 more concrete. i.e. are we going to wait for Ruby to support
0-10 before we cut M3, or will we be willing
to cut it with Java, JMS, C++ and .NET clients?
I have also moved the windows and solaris ports up into the M3 category,
as I believe those working on them want to
get them done ASAP.
I also think there are a bunch of smaller things people want to get in,
we should get these into JIRA. We also have
this comment: "Transparent 0.8/0.9/.10 support in the Java broker (might
need to be M4)" I think we need to become
concrete on what all we want to get done of the Java broker for M3.
Also, do we want to replace MINA with the IO transport on 0-8 and 0-10
Java client on trunk? What we do on the broker
is probably a longer discussion and longer term thing.
Finally, the JIRA for M3:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310520&fixfor=12312117
Well, lets just say it needs some clean-up. I can identify a bunch of
stuff that has been done but is not closed etc. We should
maybe setup a call, or tag team the list of items and make sure we have
what we want in the list for M3, and close out the
crud.
Maybe we open a bridge on the 19th or 20th for everyone that can join
and we do a M3 JIRA clean-up party... thoughts
Carl.
