Ok, stable branch is setup. http://svn.apache.org/repos/asf/openejb/branches/openejb-4.0.x/
TCK setup: https://svn.apache.org/repos/tck/openejb-tck/branches/tomee-1.0.x (not publicly accessible) Buildbot: http://ci.apache.org/builders/openejb-4-stable It took a while to stomp out all the versions. After several iterations of deleting the previous version from my maven repo, grepping the build output and building offline it seems to be in shape. Before we start merging in fixes, I'd like to get a green build and a clean TCK run. I did a run on the TCK last night and it came back green, however it clearly was setup wrong as the JAX-RS tests passed and 1.0.1 web profile has no JAX-RS support. Still some kinks to be worked out. Hammering on that now. It would be wonderful if we could release that branch monthly on a schedule, similar to Tomcat. To make that happen, I'd like to propose we be a little more strict and only merge code with a JIRA. It may prove to be too tedious, but it would be a good experiment to try. The goal would be remove as much "human" attention that the branch needs and to possibly be able to automate the release of it as much as possible so it can happen regularly (say monthly) even if people are busy. A near "push button" release. To do that, changes need to come in in near perfect condition with a clear JIRA and clear reason. If we do that, generating the release notes will be easy. We could possibly even enforce this with an SVN hook. Might be something to try for a while and see how it works out. I'm not a fan of rigid rules, but experimentation is excellent. Thoughts? -David
