We're going to have to delay the 1.0.1.CR1 release until tomorrow due to outstanding issues. Sorry about that. Pete On 18 Jan 2010, at 16:18, Pete Muir wrote: > All, > > 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 Feb. > > To this end, the release schedules are: > > CDI TCK > > 1.0.1.CR1: 21st January (Thursday this week) > 1.0.1: 4th Feb > > Weld > > 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) > > leaving > > * Pete/Unassigned - 27 issues > > Thanks! > > Pete > _______________________________________________ > weld-dev mailing list > weld-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev

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. Best, Pete 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. > > Pete > > On 18 Jan 2010, at 16:18, Pete Muir wrote: > >> All, >> >> 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 Feb. >> >> To this end, the release schedules are: >> >> CDI TCK >> >> 1.0.1.CR1: 21st January (Thursday this week) >> 1.0.1: 4th Feb >> >> Weld >> >> 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) >> >> leaving >> >> * Pete/Unassigned - 27 issues >> >> Thanks! >> >> Pete >> _______________________________________________ >> weld-dev mailing list >> weld-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/weld-dev > > > _______________________________________________ > weld-dev mailing list > weld-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev

All, please hold commits to Weld whilst I tag CR2 of Weld 1.0.1 and also a service release of the APIs. This release will also encompass the examples, SE extension, Servlet extension and support for Wicket, so please also hold commits to those modules. Thanks! On 31 Jan 2010, at 19:24, Pete Muir wrote: > Ok, CR1 is has been tagged and published to Maven. It's also integrated into JBoss AS trunk, and should soon be in GlassFish nightly builds. > > I'm not going to publish the full distro this time around - the examples etc. from Weld 1.0.0 will work fine with this release. > > We'll do a full distro for CR2 :-) > > On 29 Jan 2010, at 14:15, Pete Muir wrote: > >> 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. >> >> Best, >> >> Pete >> >> 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. >>> >>> Pete >>> >>> On 18 Jan 2010, at 16:18, Pete Muir wrote: >>> >>>> All, >>>> >>>> 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 Feb. >>>> >>>> To this end, the release schedules are: >>>> >>>> CDI TCK >>>> >>>> 1.0.1.CR1: 21st January (Thursday this week) >>>> 1.0.1: 4th Feb >>>> >>>> Weld >>>> >>>> 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) >>>> >>>> leaving >>>> >>>> * Pete/Unassigned - 27 issues >>>> >>>> Thanks! >>>> >>>> Pete >>>> _______________________________________________ >>>> weld-dev mailing list >>>> weld-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/weld-dev >>> >>> >>> _______________________________________________ >>> weld-dev mailing list >>> weld-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/weld-dev >> >> >> _______________________________________________ >> weld-dev mailing list >> weld-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/weld-dev > > > _______________________________________________ > weld-dev mailing list > weld-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev

Hello Pete, The weld archetypes are getting their component library version info from the weld-extensions-bom-1.0.0-CR2. At what point do you recommend I update the BOM version? Thanks, Steven On 02/04/2010 07:02 PM, Pete Muir wrote: > I have tagged and published to Maven version 1.0.SP1 of the APIs (containing a bug fix to the CDI API, compiling against the 2.2 EL API and improvements to the JavaDoc), and 1.0.0.CR2 of Weld. You can now commit to core again. > > We won't be integrating this release in JBoss AS straight away, as they are in a component update freeze, prior to releasing M2. Once that release is out, we will integrate this release. I know Roger is planning to integrate this release into GlassFish sometime soon. > > I've also tested the SE, Servlet and Wicket support as well as all the examples, however I have yet to tag and release these, or build the distribution zip. I'll do this tomorrow. For this reason, please hold commits to these areas until then :-) > > Pete > > On 4 Feb 2010, at 18:34, Pete Muir wrote: >

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 18 Feb 2010, at 12:12, Pete Muir wrote: > > On 29 Jan 2010, at 14:15, Pete Muir wrote: > >> 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. > > We're delaying this release for a day or so, as a number of issues have emerged on the GlassFish TCK run that we want to nail down the cause of. > > Expect the release to be complete on Monday. I will start the release tomorrow, so please check with me before making commits to any of Weld. I will start by releasing the TCK, and then move onto core, and then the other areas such as examples, integrations etc. With luck I will complete this tomorrow, and pass it to QA for testing on Monday (Ondrej, can we get time for this?). However, if I run into issues, then, as I travelling on Monday, I will continue to work on this on Tuesday. Best, Pete _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev