Development Process - PTC-ALM/TortoiseSI GitHub Wiki

Posting Issues

Issues can be posted by any collaborator (member of the TortoiseSI team). New issues that have not been categorized will be triaged by a committer (member of the TortoiseSI-committers) team, and will have appropriate labels added.

Milestones

Each issue should be assigned to a release milestone. In the 1.0 release, the integration provides ways to address the fundamental use cases of a developer working in Windows Explorer. The workflows may not be ideal, but the use cases are supported. A 1.x release stream will be allow for minor bug fixes and small features.

The intention is for the 2.0 release to include a Windows dialog for submitting changes. 1.0 uses the Integrity client's Working File Changes view, which was introduced in Integrity Lifecycle Manager 10.7. 2.0 may also include some level of folder status indications.

Labels

help wanted

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.

If one of these tasks is picked up (assigned), the help wanted label should be removed. Anything without this label is either waiting on an answer to a question, is already being worked on, or likely is missing some important details about what needs to be done.

needs docs

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 verification, the "needs verification" label should also be added.

needs verification

This label is added when an issue (such as a bug or 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 TortoiseSI 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.