The new jta code is not fully cleaned and in a public repository. Need to check with Mark/Kevin to see if this is still on target for a 4.0.4 release next month.
> -----Original Message----- > From: Adrian Brock > Sent: Friday, February 24, 2006 8:48 AM > To: Dimitris Andreadis > Cc: jboss-development@lists.sourceforge.net; Architect > Council; QA; Scott M Stark; Ivelin Ivanov > Subject: Re: Finalizing the Release of JBAS 3.2.8.SP1 & > 4.0.4.GA - YourHelp is Needed > > The JCA, JTA and JMS work is pretty much done. > > The outstanding stuff is all testing, some just to prove > there is still no problem on bugs already fixed. > > But this also includes the big one, > i.e. testing JMS inflow. > > Incidently, I thought there would be some tasks raised for > JBoss Transactions before the 4.0.4 release was finalized? > > On Fri, 2006-02-17 at 12:31, Dimitris Andreadis wrote: > > Hello everybody, > > > > We have scheduled 2 releases of JBoss AS: > > > > v3.2.8.SP1 for 03/Mar/06 (i.e. in 2 weeks time) v4.0.4.GA for > > 17/Mar/06 (i.e. in 4 weeks time) > > > > 3.2.8SP1 is needed to address a couple of issues with 3.2.8 > (JBossMQ > > -already fixed- and some extra interop scenarios with 4.0.2 > versions, > > plus whatever appears within the next 2 weeks), so it's > under control. > > > > However, getting 4.0.4.GA out the door is a big challenge > as we have > > about 290 issues open! This list needs to be reduced to a > manageable > > size of 90 or less issues to be solved until the release date. > > > > We need EVERYONE to have a close look at the JBAS JIRA > tasks related > > to his area of interest in order to: > > > > 1) Decide what features/bug/task are really important to go > out with > > 4.0.4. > > > > Remember, 4.0.4RC1 is already out so new features shouldn't > really be > > included between RC1 and GA, unless absolutely necessary, so we are > > talking about bug fixing mostly. > > > > Please make use of the task Priorities to increase to > "Critical" the > > priority of the tasks you want to get done for 4.0.4, and > decrease to > > "Minor" those you don't. > > > > 2) Assign the issues to yourself or a member of your team; allocate > > time to work and close those critical issues within the > next 3 WEEKS > > (to leave some time for testing). > > > > If you don't have time to work on those tasks, keep them unassigned > > and either postpone those for 4.0.5.CR1, or if something is never > > going to get fixed just close it as such with an explanation. > > > > If it still something important that you don't have time to work on > > and we must look at, RAISE the issue in the DEV list so we find > > someone to work on it. > > > > Again, please raise any issues, especially integration ones > EARLY in > > the DEV and QA lists. > > > > Thanks for all your help in advance. > > > > /Dimitris > -- > xxxxxxxxxxxxxxxxxxxxxxxx > Adrian Brock > Chief Scientist > JBoss Inc. > xxxxxxxxxxxxxxxxxxxxxxxx > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
