- Users will generally discover bugs and report them in the OpenG discussion forums or by sending an email to the code's author
- When a bug is submitted to the forums or an OpenG developer, the developer should file a bug report in the official OpenG Bug Tracker
- A bug may only be fixed, if a the official bug report has been assigned to them in the OpenG Bug Tracker
- Before fixing the bug, a unit test should be added into the ./tests/ folder that exposes the bug via a test failure. Fixing the bug should cause the test to pass.
- Modifications to the source code must be associated with the official Bug ID in the source code commit log message. (See Associating SVN Commits with Tracker Cases).
- When an issue is fixed a comment should be made in the bug report identifying which SVN revisions fix the issue. Ideally, include an SVN repository browse URL such as the following:
- When issue is fixed an entry should be made in the source code ./docs/ChangeLog-x.x.txt file (where x.x is the version of the library you are working on). This should look like the following:
- [ Bug 1759176 ] SetData function does not unlock data when error in is TRUE
Once all bugs for a release have been resolved you will go on to the next step: Package_Build_and_Release_Process
See Also
Fixing Bugs
