THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Make sure the contribution is posted publicly on the Apache OFBIZ JIRA issue tracker. Please do not commit changes that were sent to you privately. If you receive a patch, open a JIRA issue and then ask the submitter to post his patch there. This way, we can avoid having to get an iCLA for the contributor, as well as let everybody in the community view and comment on the contribution.
- If it is a new file, the file must have the Apache 2.0 license header.
- The commit log must identify the name of the contributor and, if relevant, the JIRA issue for it.
Following changes
Manage JIRA's issues
Please take the time to correctly fill the different Jira fields we now use for our releases change logs.
- Specifiy in Resolution :
- Improvements : use either Done or Implemented Status as you feel right
- New features : use the Implemented Status
- Bug : use the Fixed Status
- Specify in the Fix Version/s the codebase(s) to which you have committed the patch/fix :
- you can select from the dropdown one or more of the items under the "Unreleased Versions" group in the top part of the drop down box;
- you should never use one of the items in the "Released Versions" section (bottom part);
- if the fix/patch is submitted to "Trunk" then select "Upcoming Branch";
- if you are backporting/committing to a release branch then select the latest (next) release version in that branch available in the dropdown.
For example at the moment the valid items for the Fix Version/s field are :
- 12.04.06 (for commits to the branch named release12.04)
- 13.07.02 (for commits to the branch named release13.07)
- Upcoming Branch (for commits to trunk)
After some time the following Jira reports will contain very useful information :
- Road Map (what is expected in upcoming releases) : https://issues.apache.org/jira/browse/OFBIZ/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
Change Log (what is available in released packages available from the Download page) : https://issues.apache.org/jira/browse/OFBIZ/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
Note title Reminding Even if when the svn commits comments are correctly done with a reference to the Jira issue number we can then get to the commits in Fisheye from the Development section of the Jira issue, I'd still recommend to put the commits references in a comment. It's always handy, and insures we have those references at hand even if the commits comments don't contain the Jira issue reference.
Complete the documentation
- Of course it's recommended to follow what's going on on MLs, especially dev ML.
- Following changes on wiki is also recommended, one way is to subscribe to the daily email changes (in your Preferences/Watches). If you don't want to see anything about other projects you may only watch OFBiz spaces
OFBiz (Open For Business) Project Open Wiki
OFBiz End-User Documentation
OFBiz Project Administration Workspace
OFBiz Requirements and Designs
OFBiz Technical Documentation
You will be then alerted about any changes just after they have been done (with links)