THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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
- Of course you might also use other status (like duplicate, won't fix, invalid, etc.) when needed...
- 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 commit is only done (ie not backported) on "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 :
- 1213.07.04.06 (for commits to the branch named release13.07)
- 14.12.01 (for commits to the branch named release12release14.0412)
- 1315.0712.0201 (for commits to the branch named release13release15.0712)
- Upcoming Branch (for only for commits only done to trunk, ie when not backporting)
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 Reminder If 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.
Also, please put the revision number in the Jira issue. That helps others doing research on changes.
...