The QA tasks to track the release: http://jira.jboss.com/jira/browse/JBQA-311
One security case left: http://jira.jboss.com/jira/browse/JBAS-2820 And failing security related tests in the testsuite: http://jira.jboss.com/jira/browse/JBAS-2872 Need to verify that the misc-clients -> 3.2.8.SP1-server tests still work. I don't see the 3.2.x compatibility tests running. Can somebody (QA) enable them? http://jira.jboss.com/jira/browse/JBAS-2875 Maybe we need to verify the reverse testing still works, as in: http://jira.jboss.com/jira/browse/JBAS-2802 Can somebody (QA) enable this too? Any other 3.2.8.SP1 business? Misc ==== A) I've renamed 3.2.9 to 3.2.8.SP2 in the light that we'll avoid producing yet another point release in the 3.2.x branch, and come up only with bug fixing 3.2.8 Service Packs when necessary. If this is the case we don't need to branch off to a new Branch_3_2_8, we can keep using Branch_3_2 for all future 3.2.8 service pack releases. Comments? B) I have another scenario I want to test that involves tx propagation from 4.0.2 server -> 3.2.8.SP1 server. Currently we don't have any automated server->server tests. Any views on whether this should be automated? /Dimitris ------------------------------------------------------- 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
