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 :
| Warning | ||
|---|---|---|
| ||
Because we decided to not release the R14.12 and R15.12 branches, and because 13.07.03 was the last release of the R13.07 branch, currently only "Upcoming Branch" and Release Branches (like Release Branch 15.12) are available in the "Fix Version/s" field. Not released versions (like 13.07.03) will no longer appear but when we wil release the next coming R16 branch. |
- 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 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 :
13.07.04 (for commits to the branch named release13.07)14.12.01 (for commits to the branch named release14.12)15.12.01 (for commits to the branch named release15.12)
- Upcoming Branch (only for commits only done to trunk, ie when not backporting)
...