Maybe we should sneak in the openejb-lite assembly before pushing out the release?
On Jun 1, 2011, at 1:45 PM, Thiago Veronezi wrote: > Good point... how to publish a snapshot? Should it be here? > https://cwiki.apache.org/confluence/display/OPENEJB/OpenEJB+Binaries Updated that doc with the correct settings. Though I setup CI for the 3.2 branch so all the binaries should be current: http://ci.apache.org/builders/openejb-branch32 But give publishing a try anyway. > It mentions something about publishing unstable at here > http://cwiki.apache.org/OPENEJB/latest-unstable.html. Is there anything > already set for that? Can we set it? How? :O) One more out of date doc. > On Wed, Jun 1, 2011 at 1:42 AM, Jean-Louis MONTEIRO <[email protected]>wrote: > >> Never did the release so if nobody is volunteer I can try with some help. That sounds great. We need more people with release skillz. :) I try to keep this doc up to date, but each release ends up being a bit different. http://openejb.apache.org/openejb-release-process.html First step is to make sure the itests run and pass. This script usually needs updating before it runs: http://svn.apache.org/repos/asf/openejb/branches/openejb-3.2.x/assembly/test/build.xml Typically we want to update the tomcat versions. I forget, did we add Tomcat 7 support to 3.2? If so we need to add that in as well. On the note of what we added, we need to sweep through JIRA and clean up anything 3.2 related. Typically I: - individually review and close jiras that are open. - yank out any JIRAs that were filed as bugs on the release if it is clear that it wasn't actually a bug in the previous release and the person was just fixing stuff that broke while developing the new release -- we don't want to misinform users by reporting bugs that never released. - review of the commits since last release to see if anything important was forgotten and file a JIRA for it if there isn't one. - shorten the titles of long JIRAs as well so that they are more friendly in the release notes. - look for newer closed jiras that aren't currently assigned to a version and see if they apply to this release (we can probably skip that one) Not too much was done on 3.2 so it shouldn't be too bad, but the first 4.0 will be a bear :) -David
