Search results
Jump to navigation
Jump to search
- ...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 f7 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 discussion5 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. I7 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 repo6 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/quer31 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 i7 KB (1,087 words) - 00:34, 17 May 2016
- * Bugs triage6 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. I7 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. I7 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 fixes27 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. I8 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 wi8 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 is9 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. I10 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 does10 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