mantisbt:development_process
This is an old revision of the document!
Development Process
- Work should be related to an existing MantisBT issue, if no one exists, create one.
- For non-trivial bug fixes or any features, describe the suggested work in the issue.
- If you need immediate feedback from the core developers, email the dev mailing list with a pointer to your issue. The feedback should be captured directly in the issue rather than the mailing list.
- Implement the feature / fix in a branch on your fork of MantisBT on github.com and submit a pull request.
- Feedback about the work should be provided within 3-7 days.
- A pull request should include a complete change. A checkin should never block releasing waiting on follow up work.
- When applicable pull requests should be sent for stable branches.
- Master should always be open to accept contributions.
mantisbt/development_process.1389758827.txt.gz · Last modified: 2014/01/14 23:20 (external edit)