My apologies on the naming of the milestones. Nick pointed out we decided on doing two CRs instead of a M1 and CR... So that means the milestones are actually CR1 and CR2 as below. * April 29, 2011, JBDS 4.1 CR1 * May 20, 2011, JBDS 4.1 CR2 * June 17, 2011, JBDS 4.1 GA It's a small typographic difference, but it saves Nick from having to change the name of any builds. Since we're going minimalistic for this release, let's keep naming impacts to a minimum for Nick! --Fitz _______________________________ Brian Fitzpatrick (aka "Fitz") Senior Software Engineer, SOA-P JBoss by Red Hat ----- Original Message ----- From: "Brian Fitzpatrick" <bfitzpat(a)redhat.com&gt; To: external-exadel-list(a)redhat.com, "tools-dev" <jbosstools-dev(a)lists.jboss.org&gt; Sent: Thursday, April 7, 2011 5:17:08 PM Subject: [jbosstools-dev] JBoss Tools 3.2.1/JBDS 4.1 Status Update Hi all... We're now almost all the way through the first week of April and I'd like to touch base about where we are regarding JBoss Tools 3.2.1 and JBDS 4.1. At last week's JBDS PM meeting, we discussed a few dates for JBDS 4.1 milestones... April for M1, May for CR1, and a June GA. These were pretty vague dates, so I'd like to lock this down to make these dates a bit more specific. Let's shoot for: * April 29, 2011, JBDS 4.1 M1 * May 20, 2011, JBDS 4.1 CR1 * June 17, 2011, JBDS 4.1 GA I'm hopeful that a three week window between M1 and CR1 will give QE the time they need to get things done. Unfortunately, the F2F meeting falls smack dab in the middle of that and we have JBoss World early in May. That may push these dates out a bit. However, hopefully we can take advantage of the growing suites of automated tests that Jiri and his team have been building over the year. We don't have a final date for SOA-P 5.2 yet, so we may have some additional wiggle room as well. That said, we still have a lot of open JIRAs. As of this moment, we have 89 JBIDE [1] and 11 JBDS [2] JIRAs open. With 15 working days between now and the end of April, I somehow doubt we're going to close all of these. I would encourage you to take a hard look at the JIRAs for your components set for 3.2.1 and figure out if they're critical for this short release cycle. If not, bounce them to 3.2.x or one of the 3.3 milestones. If they're still important, try and get them fixed. :) If we tighten the list of bugs and knock 'em off, we should be in better shape. Thanks in advance! Back to the bugs! --Fitz [1] Open JBoss Tools (JBIDE) JIRAs set for 3.2.1: http://goo.gl/rb6AQ [2] Open JBDS (JBDS) JIRAs set for 4.1: http://goo.gl/QNHrx _______________________________ Brian Fitzpatrick (aka "Fitz") Senior Software Engineer, SOA-P JBoss by Red Hat _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev