Difference between revisions of "BugSquad/DownStream"
< BugSquad
Jump to navigation
Jump to search
m (relace bugsquad header with team header) |
|||
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>{{BugSquad | + | <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}} | ||
Revision as of 09:07, 25 June 2008
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.