THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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
...
OFBiz Release-Related Tasks
Steps for testing a revision or branch before a release:
...