8,288
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: + − + Line 60:
Line 61: − + −
moved BugSquad/ContentToEdit/Triage to BugSquad/Bug Triage: promote one level
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
One key process in any software development project is the triaging of bugs and new features. The Sugar project has been part of the triage process used by the OLPC team (See http://dev.laptop.org). The tool, [http://trac.edgewall.org/ trac], seems more than up to the task. The challenge is to define unambiguous category tags in order to make the job of triage containable and to bring clarity to what is expected of developers.
One key process in any software development project is the triaging of bugs and new features. The Sugar project has been part of the triage process used by the OLPC team (See http://dev.laptop.org). The tool, [http://trac.edgewall.org/ trac], seems more than up to the task. The challenge is to define unambiguous category tags in order to make the job of triage containable and to bring clarity to what is expected of developers.
Undoubted, a key is to define a clear [[ReleaseTeam/Roadmap|Roadmap]] and decision-making process.
Undoubted, a key is to define a clear [[Development Team/Release/Roadmap|Roadmap]] and decision-making process.
** accept
** accept
[[Category:BugSquad]]
[[Category:Developer]]