View source for The bugtracker and git


This article should help developers on the LimeSurvey when resolving issues.

General process outline:

# Bug reported by a user in [https://bugs.limesurvey.org Mantis]
# Bug assigned to a developer (by the developer or someone else)
# Bug fixed and a PR (pull request) made at github.com
# Mantis ticket status changed to '''ready for code review''', '''Assigned To''' can remain to be the developer that fixed the issue
# When creating the PR, please assign reviewer (DenisChenu or gabrieljenik for bugs, developer suggested by Github for features - suggested reviewers are based on git blame data)
# If the code review fails, reviewer puts comments in the PR what needs to be fixed
# After successful code review, quality assurance tests and verifies the bugfix/feature
# If testing fails, quality assurance puts comments in the Mantis ticket
# Finally if all is well, quality assurance merges the PR and code gets published with a new version
# Mantis ticket status changed to '''resolved''' and later '''closed'''

This method of working should allow for efficient bug fixing with multiple developers.

Please respond on what you think of this process, or what should be changed.