On Sep 10, 2006, at 6:13 PM, Christian Geisert wrote:

David E Jones schrieb:
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. The "tag" in this case is just an svn "soft" tag, ie the

So this first RC is some kind of test for the release process and the
next RC will be done from a branch where only bugfixing will happen
until the release?

Yes, this is just a "test snapshot" as described in the incubator guidelines.

Real releases, like the one we plan to do shortly after graduation from incubation, will have a branch and such. Whether we will do a branch at the release candidate phase, or even do a release candidate phase for real releases, is yet to be decided. The nature of OFBiz is quite a bit different from many open source projects and for reasons that have been discussed in probably thousands of messages over the years doing a "feature freeze" or anything like that in order to move to a "stable" release seems now to be more than the OFBiz community has resources to do properly.

Because of that the plan is to have community driven releases. In other words, we do announce a release intention and ask people to test things and if there aren't any major show-stoppers, we do a branch and a release based on that branch. Once we do a branch like this a sub-community develops that can collaborate on making that branch a good stable artifact set over time as bug fixes only are back-ported and issues specific to that branch are fixed over time.

The files are posted for initial review as attachments on the docs.ofbiz.org site to this page:
http://docs.ofbiz.org/x/wAE

I just wanted to download it but
apache-ofbiz-incubating-4.0.0.RC1.zip gives an error (root cause: java.lang.OutOfMemoryError) and apache-ofbiz- incubating-4.0.0.RC1.tgz returns a blank page.
If these files are too big for the wiki what about putting it under
people.apache.org/~jonesde ?

Yes, the Undersun server is way overloaded right now. We will be shutting down Jira on that server soon which should solve this problem for the most part.

Anyway, try it again and let me know. We had alarms go off earlier today on that server but it should all be fixed again now.

-David

Reply via email to