I'm still looking at ejb3 stuff (EJBTHREE-881 and another transient failure that popped up on cc today), but I'm not anywhere close to fixing anything. From Carlo's note earlier, I'm pretty sure other ejb3 issues are still out there as well. But I'm not too clear on how the final ejb3 things relate to tagging 4.2.0.CR1. I personally don't mind if you tag it. Dimitris Andreadis wrote: > I think we are ready to tag 4.2.0.CR1. Is there anyone still working > on Branch_4_2 ? > > The testsuites are as good as they can get; we have mostly transient > and a couple of other failures that need further investigation, but we > can do this right after the release. > > The only think left for me is to create the release notes, so I can > either tag now and re-rag the notes tomorrow (just a file) before the > distro is released, or wait for another testsuite cycle and do the > tagging tomorrow. > > What do you think? >

It's done https://svn.jboss.org/repos/jbossas/tags/JBoss_4_2_0_CR1/ Just don't release the .zip distro before I complete the release notes tomorrow. Thanks /Dimitris >> >> Dimitris Andreadis wrote: >>> I think we are ready to tag 4.2.0.CR1. Is there anyone still working >>> on Branch_4_2 ? >>> >>> The testsuites are as good as they can get; we have mostly transient >>> and a couple of other failures that need further investigation, but >>> we can do this right after the release. >>> >>> The only think left for me is to create the release notes, so I can >>> either tag now and re-rag the notes tomorrow (just a file) before the >>> distro is released, or wait for another testsuite cycle and do the >>> tagging tomorrow. >>> >>> What do you think? >>> >> >> > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development