Hi, On 9/9/06, David E Jones <[EMAIL PROTECTED]> wrote:
On this topic... I've been looking at the release stuff and decided to just go for it...
In the future a heads-up, at least to the PMC but preferably to the public ofbiz-dev list, would be appreciated ;) Such a heads-up lets other committers make sure they've committed what they're done with and reverted experiments that could negatively impact a release.
For this initial RC1 for version 4.0.0 I decided to go with the tag route and we'll do a branch later when we're ready to do a final release.
+1.
The "tag" in this case is just an svn "soft" tag, ie the implicit tag from the revision number (see the REVISION) file in the archive. A real tag in SVN is pretty much the same as a branch and I think is a little heavier than what we need for this.
OK, but just so you know SVN tags are cheap and light: it's a single (atomic) copy operation, that's it. A real SVN tag provides people with easy ways (including easily scriptable ways) to recreate past builds without needing to find the corresponding text file and read it.
1. test un-archive and run as-is (should only require JDK installed) 2. identify and show-stopper bugs that we should fix before a real RC 3. check all ASF required files (NOTICE, LICENSE, KEYS, etc) and headers 4. check PGP and MD5 files 5. anything else?
Are there any automated unit tests done as part of the release creation? If so, the person cutting the release should also let us know whether they all passed (hopefully), or if any failed, which ones.
The files are posted for initial review as attachments on the docs.ofbiz.org site to this page: http://docs.ofbiz.org/x/wAE
Since this is a public page, please add a clear disclaimer to let people know this is not an official release and hasn't been vetted by the PMC. Yoav
