OK just a retransfer:P<br><br><div class="gmail_quote">2012/10/3 Kate Stewart <span dir="ltr"><<a href="mailto:kate.stewart@canonical.com" target="_blank">kate.stewart@canonical.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear Developers,<br>
<br>
After tracking down and resolving several blueprints that weren't<br>
labeled properly so they'd get into the list[1] for R series and UDS<br>
planning, it seemed like a refresher of the conventions to use<br>
might be appropriate. ;)<br>
<br>
When registering a blueprint, most efficient way to get it created<br>
and sorted into the right place is to "Register a Blueprint" from<br>
r-series page [1]. Some conventions to follow:<br>
* Name: of blueprint should be of the form <track>-r-<topic name><br>
* Propose for sprint: "Ubuntu Developer Summit-R"<br>
* Click on propose for series goal<br>
<br>
There are also some draft conventions[2] for the content to put in<br>
the blueprint that will permit automation. There will be a separate<br>
email to discuss those further. Would like to come to closure on this<br>
at UDS-R on standard format for all of us to use, so we can start making<br>
effective use of bots to help with the housekeeping tasks...<br>
<br>
And on that note ;), could approvers and assignees of blueprints,<br>
please take a pass through the current set of blueprints [3], and make<br>
sure they all are up to date by 10/4 1200 UTC. We'll be using the<br>
information in them to generate the first pass of the 12.10 Release<br>
Notes, and only picking up information from those marked "Beta<br>
Available" or "Complete". Specifically we'll be looking for text in<br>
the "Release Note:" section of the whiteboard. If a line item is<br>
clearly now not going to make it, please mark it as postponed.<br>
<br>
We'll be using [5] to summarize the feedback and results of working<br>
with the prototype this release, possibly spinning out a separate<br>
blueprint to continue the evolution, based on feedback added. As you<br>
work through the blueprints, and other issues emerge, feel free to add<br>
them to the Whiteboard on [5].<br>
<br>
Thanks for your help with this,<br>
Kate<br>
<br>
[1] <a href="https://blueprints.launchpad.net/ubuntu/r-series" target="_blank">https://blueprints.launchpad.net/ubuntu/r-series</a><br>
[2] <a href="https://wiki.ubuntu.com/BlueprintSpec" target="_blank">https://wiki.ubuntu.com/BlueprintSpec</a><br>
[3] <a href="https://blueprints.launchpad.net/ubuntu/quantal" target="_blank">https://blueprints.launchpad.net/ubuntu/quantal</a><br>
[4] <a href="https://blueprints.launchpad.net/ubuntu/+spec/other-q-release-notes" target="_blank">https://blueprints.launchpad.net/ubuntu/+spec/other-q-release-notes</a><br>
[5]<a href="https://blueprints.launchpad.net/ubuntu/+spec/foundations-r-prior-release-feedback" target="_blank">https://blueprints.launchpad.net/ubuntu/+spec/foundations-r-prior-release-feedback</a><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Ubuntu-release mailing list<br>
<a href="mailto:Ubuntu-release@lists.ubuntu.com">Ubuntu-release@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-release" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-release</a><br>
</font></span></blockquote></div><br>