On 14/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
I was about to respond with a similar suggestion, but even less aggressive in terms of features. What we'd like to see is an M2 starting essentially right away, shortly after Rajith branches for M1. We'd like to scope M2 to include maven, along with a move to junit3 so as to enhance the effectiveness of maven and enforce the jdk 1.4 constraint for client.
What kind of timescale do you think is realistic for M2? My only issue with the above is that it does not offer anything in the way of extra functionality for our users so if due to the overhead of the Apache release process that took a while we would be spending time on admin etc. It's tangential to this discussion but for jdk 1.4 support IIRC there was discussion about use of Retroweaver. I believe it would actually be nice to further consolidate broker and client code (there is stuff that is basically duplication) and that implies 1.5 source.
What would specifically *not* be in M2, however, would be a move to the new rev of AMQP -- we'd push that off to M3 (note BTW that this requires going through JIRA to move all relevant issues related to AMQP version from M2 to M3).
Yes, agreed.
Whether persistence and JMS could be in the picture, I hadn't considered. I don't know how close persistence is, nor how much work the JMS stuff is, but we can certainly talk about that.
I will be able to give a better indication later this week on how I think persistence is going (I think it's going well but wouldn't want to state anything categorical until I had joined up all the dots, and got some feedback from someone else). RG
