Search results

Jump to navigation Jump to search
  • ...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

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)