Difference between revisions of "BugSquad/DownStream"

From Sugar Labs
Jump to navigation Jump to search
m (TestingTeam/DownStream moved to BugSquad/DownStream: Robot: moved page)
m (Robot: Automated text replacement (-TestingTeam +BugSquad))
Line 1: Line 1:
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>{{TeamHeader|TestingTeam}}
+
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>{{TeamHeader|BugSquad}}
 
{{stub}}
 
{{stub}}
  
Line 10: Line 10:
  
  
[[Category:TestingTeam]]
+
[[Category:BugSquad]]

Revision as of 17:27, 16 December 2008

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

This article is a stub. You can help Sugar Labs by expanding it.

Good Communication with downstream distributions is essential for receiving bug reports and patches from outside developers.

Create Policies for Accepting Bug Reports and Patches from Downstream

Develop Patch Management Policies

As a new project, Sugar is in a unique position of developing patch management policies based on the best practices of other similar projects.