-
Notifications
You must be signed in to change notification settings - Fork 8
Development Process
Issues can be posted by any collaborator (member of the TortoiseSI team). New issues that have not been categorized will be triaged in the regular backlog refinement sessions, and will have appropriate labels added.
Each issue will be "committed" to a sprint milestone. Issues that haven't been completed by the end of their committed sprint will be moved to the next sprint. Each sprint is one week long, ending on Thursdays. To be included in the weekly sprint reviews, please contact [email protected].
This label will apply to any item (open or closed) that should be documented in the HTML user documentation. After documentation is in place, the label should be removed. If the documentation needs verificaation, the "needs verification" label should be added.
This label is added when an issue (bug, enhancement) is ready for testing. To verify an issue, add a comment about how the issue was tested, and what build it was tested in. As appropriate, a PTC team member will take the verification steps and add them to an internal Integrity Test Suite, so that the same verification steps can be executed for regression testing, prior to an official release build. A PTC team member will also close the issue, after it has been reviewed in a sprint review session.
This label is applied to anything that is a reasonably separate piece of functionality, and there is an expectation that enough information has been provided in the issue description for anyone to contribute to the implementation.