2009/10/14 David Ingham <[email protected]>: > Hi all, > > I just wanted to let you know that we're planning on showcasing Qpid at the > upcoming Microsoft PDC (Professional Developers Conference) [1]. We're > planning a session focused on queuing and pub/sub in a heterogeneous > environment. This will cover existing bridging solutions as a way to connect > different islands of message-oriented middleware and then talk about the > value of AMQP as an interoperable wire-level protocol. We aim to include an > AMQP/Qpid demo that connects Java/JMS, WCF, and Excel clients. > > I think this is a great opportunity for us to introduce Qpid to the Microsoft > developer community. During the talk we'll direct the interested members of > the audience to qpid.apache.org to download the bits. It would be great if we > had the 0.6 release ready and waiting for them when we announce this. The > conference runs November 17-19. Do you think we'll be ready to hit this date? > > Thanks, > > Dave. > > [1] http://microsoftpdc.com/ >
Hi Dave, I'd like to think we could pull together to get the release done for then but historically we are not very good at getting the releases out. The 0.5 Release schedule was : End of Development : 2009-03-02 End of Feature Freeze : 2009-03-16 Release : 2009-03-27 from: http://markmail.org/message/ac74jgyrymuazyth?q=Release+Schedule+qpid-dev+list:org%2Eapache%2Eincubator%2Eqpid-dev&page=1 Which gave us two weeks of bug fix testing then two weeks for voting. We did follow those dates but there were some last minute changes on the Java side that caused us to slip, to May 28th for the release announcement. Four weeks is tight for a release based no previous releases but the first step if we want to target November 17th then we need to get a release schedule together asap so we can get agreement from the community. Martin -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
