Search results
Jump to navigation
Jump to search
Page title matches
- ...how | pt =show | ro =show | ru =show | sv =show }}</noinclude>{{TeamHeader|BugSquad}} Good Communication with downstream distributions is essential for receiving bug reports and patches from outsi734 bytes (106 words) - 20:15, 24 February 2010
Page text matches
- ...how | pt =show | ro =show | ru =show | sv =show }}</noinclude>{{TeamHeader|BugSquad}} Good Communication with downstream distributions is essential for receiving bug reports and patches from outsi734 bytes (106 words) - 20:15, 24 February 2010
- Minutes at [[BugSquad/Meetings/Minutes/2008-12-10]] ==SL Community Bugsquad==3 KB (562 words) - 20:16, 24 February 2010
- * Agenda at http://sugarlabs.org/go/BugSquad/Meetings/Agendas/2008-12-17 ** http://sugarlabs.org/go/BugSquad/Mission (got accepted)2 KB (368 words) - 20:16, 24 February 2010
- <noinclude>{{TeamHeader|BugSquad}} [[Category:BugSquad]]2 KB (289 words) - 16:21, 14 May 2016
- ** http://sugarlabs.org/go/BugSquad/Mission ** maybe coordinated with downstream testing sprints?631 bytes (99 words) - 20:16, 24 February 2010
- ...cruit it. See my and Walter notes about the verification process on [[Talk:BugSquad/ContentToEdit/Triage]]. ...which does external trackbacks to tickets (useful for monitoring upstream/downstream trac instances, for instance).11 KB (1,772 words) - 14:47, 6 June 2019
- ...leaves, both upstream with those packaging the GNU/Linux distributions and downstream with those packaging Sugar for deployment on specific hardware or doing a S ...appreciate more feedback regarding the upcoming Sugar Release 0.84 (See [[BugSquad/Triage Guide#How_to_get_up_to_speed|the Triage Guide]]). Also, Tomeu Vizoso7 KB (1,128 words) - 19:37, 27 July 2010
- ...ackages had not been tested at all, so we all need to test the work of our downstream packagers, and help them where possible. ===== Form the Sugar Labs Bugsquad =====59 KB (8,636 words) - 17:29, 10 April 2018