Page History

...

All commits require an associated JIRA except in obvious cases where creating a JIRA to track the unit of work does not make sense. For example, if the initial commit did not include a file, no JIRA is necessary to commit the missing file. Comment changes and changes to most example code do not require a JIRA.  We use common sense to minimize the burden of releasing code for the programer as much as possible, but we must also balance this with a need to track all changes in JIRA.

Resolving the JIRA

Resolve the JIRA using the following template:

Tested-with:

• List of tests that you ran to verify the bug fix (and which platforms, if applicable)

Unit Tests:

• Include a list of the regression tests
• If a regression test is not applicable please add a noreg label, e.g. noreg-hard.

When the change set is visible on the mailing list, 

• Link to the changeset URL

Example

The following is a good example of the process: RT-nnnnn (//TODO - add section on Bug processing: add an example)