Search results

Jump to navigation Jump to search

Page title matches

  • 346 bytes (52 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
  • ...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
  • 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
  • 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 gettin
    2 KB (368 words) - 20:16, 24 February 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 developers
    384 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 especial
    1 KB (181 words) - 19:37, 27 July 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
  • # 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 triag
    787 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 applica
    3 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 (c
    4 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.or
    2 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
  • * Triage [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new
    6 KB (1,105 words) - 00:37, 17 May 2016
  • ...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
  • ...e landed bug fixes carefully. A friendly [[BugSquad]] will be available to triage those bugs accordingly.
    3 KB (386 words) - 16:17, 6 October 2009
  • ...ery *very* high-level assessment of bugs to be moved over. Basic, *basic* triage from knowledgeable developers.
    3 KB (394 words) - 21:33, 23 February 2010
  • ...Sugar Release 0.84 (See [[BugSquad/Triage Guide#How_to_get_up_to_speed|the Triage Guide]]). Also, Tomeu Vizoso is trying to organizing more direct feedback f
    7 KB (1,128 words) - 19:37, 27 July 2010
  • ...pic suggestion before the start of a board meeting. The meeting chair will triage discussion-topic requests. To increase the likelihood that your discussion
    5 KB (780 words) - 19:37, 27 July 2010
  • 5. In the run up to string freeze for Release 0.86, Simon Schampijer led a triage session (See [https://bugs.sugarlabs.org/milestone/0.86 Milestone 0.86]).
    5 KB (831 words) - 09:09, 12 August 2010
  • ...are able to fix them in time. A friendly [[BugSquad]] will be available to triage those bugs accordingly and the developers can never have enough bug food. I
    7 KB (946 words) - 00:09, 3 July 2009
  • As you file and review bugs, you can help triage bugs by finding duplicates and sharing questions and comments with the repo
    6 KB (985 words) - 14:41, 6 June 2019
  • | Sugar Triage || align=left | Organize a triage meeting to review/assign open sugar bugs [http://bugs.sugarlabs.org/query?s | Activities Triage || align=left | Organize a triage meeting to review/assign open activity bugs [http://bugs.sugarlabs.org/quer
    31 KB (4,396 words) - 00:58, 21 November 2013
  • ...useful in the field for teacher-trainers and onsite developers to quickly triage problems as the crop up. It would be useful for the students and teachers i
    7 KB (1,087 words) - 00:34, 17 May 2016
  • * Bugs triage
    6 KB (880 words) - 07:45, 13 October 2013
  • ...shape for the final release. A friendly [[BugSquad]] will be available to triage those bugs accordingly and the developers can never have enough bug food. I
    7 KB (962 words) - 16:26, 18 September 2009
  • ...and please report any issues you find. The BugSquad is still available to triage bugs.
    6 KB (938 words) - 19:37, 27 July 2010
  • ...shape for the final release. A friendly [[BugSquad]] will be available to triage those bugs accordingly and the developers can never have enough bug food. I
    7 KB (970 words) - 13:08, 13 September 2009
  • (04:29:02 PM) erikos: b) we should maybe do daily triage meetings until we have 0.86 is out (04:36:16 PM) erikos: tomeu: maybe we should ask as well who is around for triage and bug fixes
    27 KB (4,030 words) - 21:33, 23 February 2010
  • ...are able to fix them in time. A friendly [[BugSquad]] will be available to triage those bugs accordingly and the developers can never have enough bug food. I
    8 KB (1,262 words) - 00:07, 3 July 2009
  • ...e spent this week fixing blocker bugs for the next release, doing a lot of triage and several patch reviews. He implemented an improved logic handling new wi
    8 KB (1,242 words) - 08:27, 19 December 2016
  • Most of the early effort will be developing a triage guide and working through the backlog of bugs. Where appropriate, David is
    9 KB (1,375 words) - 08:26, 19 December 2016
  • ...n good shape for the release. A friendly [[BugSquad]] will be available to triage those bugs accordingly and the developers can never have enough bug food. I
    10 KB (1,514 words) - 10:03, 11 September 2009
  • (06:54:09 PM) erikos: tomeu: we need to schedule triage sessions, and fix bugs (07:19:59 PM) bemasc: We also need to triage all the bugs in trac, but only the release manager can really do this.
    38 KB (6,004 words) - 21:33, 23 February 2010
  • ...arlabs Bugsquad, the quality assurance (QA) team for Sugar. The squad will triage bugs, set priorities, verify usability and test cases. Furthermore it does
    10 KB (1,699 words) - 09:33, 19 December 2016
  • ...nt Events/2010-03-07|2010-02-28]] There are many ways to contribute to the triage effort...
    22 KB (3,188 words) - 20:10, 6 November 2017
  • :'''<walterbender>''' Other than a few details: a server, triage in on important area, it is about support and coordination that we are inte
    36 KB (6,435 words) - 23:22, 1 March 2011
  • ...d|bug squad]] and [[BugSquad/Meetings|helping]] to [[BugSquad/Triage Guide|triage]], or actually helping fix some small [http://tinyurl.com/ctfkjl bug] (we'v
    38 KB (5,778 words) - 20:38, 22 December 2016
  • :'''<marcopg>''' like the bug triage team lead
    43 KB (7,925 words) - 09:34, 1 March 2011
  • :'''<tomeu>''' makes triage sessions quite a bit faster
    39 KB (7,263 words) - 09:35, 1 March 2011
  • * triage squad
    59 KB (8,636 words) - 17:29, 10 April 2018