Luke,<div><br></div><div>Neat. Thanks for putting down the workflow so very clearly.</div><div><br></div><div>Regards,</div><div><br></div><div>Manu<br><br><div class="gmail_quote">On Mon, Aug 16, 2010 at 9:48 PM, Luke Faraone <span dir="ltr"><luke@faraone.cc></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi all,<br>
<br>
The users of Activity Central's products and services will be running on<br>
both Debain and Ubuntu-based systems, so as an organization want to work<br>
to make both releases as strong as possible.<br>
<br>
To ease the maintenance burden as well as to share solutions to problems<br>
for mutual benefit, I'm proposing these guidelines for members of the<br>
Ubuntu SugarTeam to follow after a problem is reported:<br>
<br>
== Handling a new bug report ==<br>
Does the problem also exist in Debian? Also report in the BTS.<br>
<br>
Does the problem exist in normal supported Sugar releases? Also report<br>
in Sugar Labs Trac.<br>
<br>
== Applying patches to fix bugs ==<br>
<br>
As soon as a fix is identified, verify if it works in Debian and on<br>
upstream Sugar (if applicable). Author a quilt patch with properly<br>
formatted DEP3[1] headers, linking to the bug numbers (Ubuntu, Debian,<br>
and SL) and providing a description of the patch itself.<br>
<br>
Patches to bugs in Ubuntu are generally preferred as a debdiff against<br>
the previous version, attached to the bug.<br>
<br>
Submit the patch to Debian and Sugar Labs *before* applying the patch in<br>
Ubuntu. If possible (ie. not under strict deadlines), wait for feedback<br>
on the patch before submitting it for inclusion in Ubuntu.<br>
<br>
For non-core sugar packages (most activities), the patch can be directly<br>
included in alioth git by members of collab-maint. A bug should still be<br>
filed against the BTS in this instance to track the issue, and the bug<br>
marked pending once it is staged in the git tree.<br>
<br>
Jonas: for core sugar packages, would you rather receive the patches as<br>
bug reports as opposed to direct commits? If patches, would you prefer<br>
debdiffs, or just the quilt patch?<br>
<br>
Does this policy seem acceptable to everyone?<br>
<br>
Thanks,<br>
<br>
╒═════════════════════════════════════════════════════════════════╕<br>
<font color="#888888">│Luke Faraone ╭Debian / Ubuntu Developer╮│<br>
│<a href="http://luke.faraone.cc" target="_blank">http://luke.faraone.cc</a> ╰Sugar Labs, Systems Admin╯│<br>
│PGP: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 │<br>
╘═════════════════════════════════════════════════════════════════╛<br>
<br>
</font><br>--<br>
Ubuntu-sugarteam mailing list<br>
<a href="mailto:Ubuntu-sugarteam@lists.ubuntu.com">Ubuntu-sugarteam@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-sugarteam" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-sugarteam</a><br>
<br></blockquote></div><br></div>