Aidan,
back to the release schedule, I think the schedule is fine, can we also
set the date for M3 March, week 11 to pick a date. I would expect that to be
C++ Broker & client 0-10
Java Client 0-10 & 0-8/9?
Python Client 0-10 (speaks all versions)
.NET 0-10 will M2 be 0-8/9 and M2 0-10 only in the client.
Ruby 0-10.
I believe we would have a Java broker with merged M2.1 and ready for
0-10, but most like not supporting 0-10 fully yet.
Carl.
Aidan Skinner wrote:
Hello all, hope you had a good break. :)
We talked about finishing the M2.1 release at the F2F and doing
quaterly releases, so I'm proposing that we aim to get M2.1 out on
Wednesday 2008-04-02, with a code freeze (ie. important bug fixes
only, no new features) on that branch from Friday 2008-02-22 so we
have some time for testing. I'll act as release manager for this now I
(nearly) have the right bits unless there are objections from other
volunteers. ;)
In parallel to this, I'll start doing the merge of M2 with trunk on a
branch (taken from and tracking trunk), I'm currently beating git with
a stick so I can use it's better merge capabilities.
- Aidan
