Changes between Version 55 and Version 56 of BugTriage0.9.2


Ignore:
Timestamp:
Apr 12, 2008, 6:58:03 AM (16 years ago)
Author:
hamish
Comment:

update url to osgeo trac

Legend:

Unmodified
Added
Removed
Modified
  • BugTriage0.9.2

    v55 v56  
    33== How does this work? ==
    44
    5 This is our second bug triage (following on the great success of [wiki:BugTriage0.9.1]). The idea is that participants will claim 5 bugs each for the upcoming 0.9.2 release and squash them! There is no bug bounty, no t-shirt prize, just a permanent record below that you have contributed in to make QGIS just that little bit more stable, less quirky and more user friendly. We encourage you to pick the 5 most easy bugs you can find in the [https://svn.qgis.org/trac/query?status=new&status=assigned&status=reopened&milestone=Version+0.9.2&order=priority 0.9.2 Milestone queue] and assign them to yourself and then fix them before January 15 2008. By getting rid of the easy to fix bugs we can improve the overall fit & finish of QGIS and make the bug queue more manageable so we can focus on the more tricky to fix bugs without any 'bug noise'. If you see things in the application that are broken, we even encourage you to open bugs for them, assign them to yourself and fix them. Easy huh?
     5This is our second bug triage (following on the great success of [wiki:BugTriage0.9.1]). The idea is that participants will claim 5 bugs each for the upcoming 0.9.2 release and squash them! There is no bug bounty, no t-shirt prize, just a permanent record below that you have contributed in to make QGIS just that little bit more stable, less quirky and more user friendly. We encourage you to pick the 5 most easy bugs you can find in the [https://trac.osgeo.org/qgis/query?status=new&status=assigned&status=reopened&milestone=Version+0.9.2&order=priority 0.9.2 Milestone queue] and assign them to yourself and then fix them before January 15 2008. By getting rid of the easy to fix bugs we can improve the overall fit & finish of QGIS and make the bug queue more manageable so we can focus on the more tricky to fix bugs without any 'bug noise'. If you see things in the application that are broken, we even encourage you to open bugs for them, assign them to yourself and fix them. Easy huh?
    66
    77== No Developer Access? ==