All, I am about to start testing for CR1, so please don't commit without checking with
me first until further notice.
The eagle eyed amongst you will notice that I added a CR2 to our release schedule for
1.0.1. A couple of issues came up at the last minute that we should fix for 1.0.1, but are
too risky to fix now. As we want to meet the JBoss AS M2 deadline (and provide a chance
for people to test what we have so far) I decided to keep this release, and add the CR2.
We will aim to release CR2 on the 4th Feb, and 1.0.1 on the 18th (as I am on PTO from 6th
- 13th). We will hold the 1.0.1 of the TCK until then to reduce the release burden.
On 28 Jan 2010, at 15:34, Pete Muir wrote:
We're going to have to delay the 1.0.1.CR1 release until tomorrow
due to outstanding issues.
Sorry about that.
On 18 Jan 2010, at 16:18, Pete Muir wrote:
> As previously discussed, we are aiming for a 10-12w release cycle of patch releases
for Weld and for the CDI TCK. This means the 1.0.1 releases should happen around the 4th
> To this end, the release schedules are:
> CDI TCK
> 1.0.1.CR1: 21st January (Thursday this week)
> 1.0.1: 4th Feb
> 1.0.1.CR1: 28th January (Thursday next week)
> 1.0.1: 4th Feb
> If you are working on issues for 1.0.1 please review the issues you are assigned, and
check that you think you can make the CR1 dates above. If you can't, please ping me
and we can either slip the issue to 1.0.1 or find some help for you.
> Current assignments by the numbers are:
> * Aslak - 1 issue (WELD-362)
> * Dan - 2 issues (WELD-27, WELD-287)
> * David - 3 issues (WELD-4, WELD-337, WELD-365)
> * Marius - 10 issues (WELD-291, WELD-269, WELD-312, WELD-325, WELD-36, WELD-314,
WELD-377, WELD-356, WELD-272, WELD-274)
> * Nik - 4 issues (WELD-32, WELD-271, WELD-361, WELD-348)
> * Roger - 5 issues (WELD-273, WELD-30, WELD-206, WELD-31, WELD-303)
> * Shane - 1 issue (WELD-257)
> * Stuart - 2 issue (WELD-335, WELD-309)
> * Pete/Unassigned - 27 issues
> weld-dev mailing list
weld-dev mailing list