Hi, folks. Our schedule (appended below) calls for all major features to
be functionally complete and on trunk by the 16th, this Wednesday.
This means we are rapidly approaching the point where we make choices. If
something won't be ready in time, we need to kick it to the next release.
We can make exceptions for changes that don't threaten to destabilize the
release. If you'd like an exception, it's quite important that we discuss
it now.
I'll begin running the release scripts tomorrow in order to discover any
new issues for the alpha release.
Thanks,
Justin
---
0.10 feature and improvement jiras:
http://bit.ly/h3Q7Sk
0.10 schedule:
16 Feb
- Alpha
- Trunk remains open
- Feature integration ends
- The alpha release tests the release process after the
introduction of major features
2 Mar, 2 weeks later
- Beta
- Branch for release (trunk remains open)
- Release branch commits require approval
- Release manager produces outstanding bug report, triages bugs
16 Mar, 2 weeks later
- RC1
23 Mar, 1 week later
- RC2
30 Mar, 1 week later
- RC3
- Targeted release date
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
