Search results
Jump to navigation
Jump to search
Page title matches
- 346 bytes (52 words) - 20:16, 24 February 2010
- 4 KB (717 words) - 11:39, 1 April 2010
- == Notes from the 0.88 triage effort == ....88. We allocated them in groups of 20 to the people who showed up for the Triage Day session in #sugar-meeting. There was some confusion about goals, but we2 KB (297 words) - 17:08, 3 March 2010
- #REDIRECT [[Talk:BugSquad/Bug Triage]]38 bytes (5 words) - 11:39, 1 April 2010
- ...allenge 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. ...ntToEdit/Triage|'''discussion page''']] for ideas about how to improve the Triage process.2 KB (230 words) - 11:39, 1 April 2010
- ...lter notes about the verification process on [[Talk:BugSquad/ContentToEdit/Triage]]. :* Good candidate for triage guidelines! --[[User:Marcopg|Marcopg]]11 KB (1,772 words) - 14:47, 6 June 2019
- ...hing, but we could have a "When things go wrong" page on the wiki that the triage team gradually help building (credits to Pamela Jones for the idea). -- [[U205 bytes (38 words) - 11:34, 1 April 2010
- The [[BugSquad/Triage Guide/Stock Responses]] are general examples of the kinds of comments that The [[BugSquad/Status Fields]] describe the fields you can use to triage the bugs in Trac.4 KB (652 words) - 11:27, 1 April 2010
- #REDIRECT [[Talk:BugSquad/Triage Team]]39 bytes (5 words) - 11:34, 1 April 2010
- 3 KB (451 words) - 12:30, 2 March 2010
Page text matches
- ** triage meetings? * Triage Policy:631 bytes (99 words) - 20:16, 24 February 2010
- ...allenge 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. ...ntToEdit/Triage|'''discussion page''']] for ideas about how to improve the Triage process.2 KB (230 words) - 11:39, 1 April 2010
- ** schedule weekly triage meetings (especially to get people started, but things should be setup so t ...an always triage at any time, and if you'd like to schedule your own sugar triage sprint, please do and announce it $here! if you're new and want help gettin2 KB (368 words) - 20:16, 24 February 2010
- ...hing, but we could have a "When things go wrong" page on the wiki that the triage team gradually help building (credits to Pamela Jones for the idea). -- [[U205 bytes (38 words) - 11:34, 1 April 2010
- ...e BugSquad is to be responsive to incoming bug reports. The Squad needs to triage the bugs and work towards a solution with the reporters and the developers384 bytes (64 words) - 20:16, 24 February 2010
- {{Transclude|BugSquad/Triage Guide}}164 bytes (15 words) - 22:54, 19 March 2010
- 1. Tomorrow (Monday, 1 March) is Triage Day for the next Sugar release: Sucrose 0.88. We'll be meeting on irc.freen There are many ways to contribute to the triage effort: feedback from the Sugar users in field about priorities is especial1 KB (181 words) - 19:37, 27 July 2010
- :* Good candidate for triage guidelines! --[[User:Marcopg|Marcopg]]825 bytes (132 words) - 11:16, 1 April 2010
- The [[BugSquad/Triage Guide/Stock Responses]] are general examples of the kinds of comments that The [[BugSquad/Status Fields]] describe the fields you can use to triage the bugs in Trac.4 KB (652 words) - 11:27, 1 April 2010
- ...gone through all 50 tickets or you think the volunteer understands how to triage.1 KB (188 words) - 11:36, 7 August 2009
- == Notes from the 0.88 triage effort == ....88. We allocated them in groups of 20 to the people who showed up for the Triage Day session in #sugar-meeting. There was some confusion about goals, but we2 KB (297 words) - 17:08, 3 March 2010
- # Triage the features into 3 lists.2 KB (261 words) - 16:13, 30 August 2009
- ...ery welcoming clique. Best way to get started is by reading the [[BugSquad/Triage Guide]] and to join us at #sugar on irc.freenode.net or in one of our triag787 bytes (117 words) - 01:10, 14 April 2010
- ...other application's talk pages; and any other community tasks such as bug triage or wiki cleanup. Feel free to call attention to any of this in your applica3 KB (463 words) - 11:25, 10 April 2009
- : Please see the [[BugSquad/Triage Guide]] -- [[User:Erikos|Erikos]]1 KB (182 words) - 13:50, 3 July 2012
- ...ng, reporting bugs, and joining in our triage efforts. We will be having a triage session next Monday, 1 March 2010, at 9 EST (14 UTC) on irc.freenode.net (c4 KB (587 words) - 14:46, 3 July 2012
- ...e landed bug fixes carefully. A friendly [[BugSquad]] will be available to triage those bugs accordingly.2 KB (275 words) - 12:37, 11 October 2009
- ...hemisphere). Time to do some spring cleaning. We'll be holding a day-long triage meeting tomorrow (Wednesday, 23 April) to try to clean up bugs.sugarlabs.or2 KB (240 words) - 13:24, 15 May 2014
- * On Sunday we had a '''[[EduJAM/2011/Brainstorm|brainstorm session]]''' to triage bug reports from the field.2 KB (264 words) - 22:08, 16 May 2011
- ...nyone can be helpful. Best way to get started is by reading the [[BugSquad/Triage Guide]] and to join us at #sugar on irc.freenode.net.2 KB (289 words) - 16:21, 14 May 2016