607
edits
Changes
New page: To land new versions of glucose and new activities in the OLPC builds we need to: * Provide test cases for each new feature or bug fix. * Find testers to execute the test cases. A way to...
To land new versions of glucose and new activities in the OLPC builds we need to:
* Provide test cases for each new feature or bug fix.
* Find testers to execute the test cases.
A way to handle it in a distributed way and ensure it's done consistently is:
* Ensure that every fix or new feature is associate to a trac ticket and that the git log for each of the related commits contain a reference to the bug.
* Before closing the ticket make sure that it contains a comment with the test case (mark it by inserting a keyword in the text so that it can be extracted automatically.
* When releasing a module, use a script to automatically generate the NEWS from the ticket references in the git log and the test cases (git log -> ticket -> test case). Put both in the release announcement.
* Provide test cases for each new feature or bug fix.
* Find testers to execute the test cases.
A way to handle it in a distributed way and ensure it's done consistently is:
* Ensure that every fix or new feature is associate to a trac ticket and that the git log for each of the related commits contain a reference to the bug.
* Before closing the ticket make sure that it contains a comment with the test case (mark it by inserting a keyword in the text so that it can be extracted automatically.
* When releasing a module, use a script to automatically generate the NEWS from the ticket references in the git log and the test cases (git log -> ticket -> test case). Put both in the release announcement.