THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
NOTE DEJ20060909: This document is still being created and is not a final draft, but should contain most of the operations needed to create a release. We may want to add more sections on preparing for a release such as more on testing, and stuff on the NOTICE, LICENSE, KEYS, etc files.
General Goals, Policies and
...
Process
How Do I Decide What to
...
Use?
From a project user perspective there is one main question that can help determine which way they will want to get OFBIZOFBiz: Do I want to contribute to the open source project?
...
- Get the code straight from the code repository (SVN) trunk and update frequently through development, and periodically even after production deployment
- Get the code from the code repository (SVN) release branch and keep updated or patched regularly as fixes are committed and the branch stabilizes over time; when getting started choose the most recent branch, even if it is very new; when new release branches are created update to them soon after the branch is done
- Get a built release package or the code from a release branch tag, and update as new pre-built release packages and tags are created; these will only represent fixes and unless a major issue arises they will be backward compatible and generally safe to update or patch to; when getting started choose a release branch that has been around for at least 2-3 months and that has no major outstanding issues in the issue tracker to assure that it has stabilized; when new release branches are created wait until you are ready to do a major upgrade and possibly need to modify your code and configuration, and wait at least until the prospective branch has stabilized before moving to it
General Release
...
Policies
- Release branches will be created approximately once per year; these will represent a new minor version number, and in cases of major and/or non-backward compatible changes a major version number
- The trunk will never go into a feature-freeze state but rather development will continue and contributions will be accepted both immediately before and after the cutoff revision for a release branch
- An initial pre-built package will be created and made available to help get people started with the branch
- Once a release branch stabilizes an initial "stable" release tag and pre-built package will be issued
- Patches on the release branch can be created and applied whenever users desire
- Follow on release tags and pre-built packages will be issued when major problems are discovered and fixed, and periodically to represent a significant number of fixes and updates
- Each new release tag and pre-built package with be represented by a third position version number change
How to do an OFBiz Release
...