x

Main chapters

  1. LimeSurvey Cloud vs LimeSurvey CE
  2. LimeSurvey Cloud - Quick start guide
  3. LimeSurvey CE - Installation
  4. How to design a good survey (Guide)
  5. Getting started
  6. LimeSurvey configuration
  7. Introduction - Surveys
  8. View survey settings
  9. View survey menu
  10. View survey structure
  11. Introduction - Questions
  12. Introduction - Question Groups
  13. Introduction - Surveys - Management
  14. Survey toolbar options
  15. Multilingual survey
  16. Quick start guide - ExpressionScript
  17. Advanced features
  18. General FAQ
  19. Troubleshooting
  20. Workarounds
  21. License
  22. Version change log
  23. Plugins - Advanced
 Actions

The bugtracker and git

From LimeSurvey Manual

Revision as of 12:19, 9 August 2012 by Sammousa (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

General process outline.

1. Bug reported by user.

2. Bug assigned to developer (by the developer himself or someone else)

3. Bug fixed in fork on github.com (each developer has his own fork?)

4. Pull request generated on github.com

5. Issue assigned to LimeSurvey repository owner (c_schmitz), status set to resolved.

6. Pull request fulfilled and bug status set to closed (done by c_schmitz)

This method of working should allow for efficient bug fixing with multiple developers without getting c_schmitz overworked..?

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

Retrieved from "http://www.limesurvey.org/manual/index.php?title=The_bugtracker_and_git&oldid=3333"