The prioritized list has been discussed in a number of venues, and has general acceptance. Chuck is having regular management mtgs (weekly) so I intend to put this priority list in front of this group every week to make sure that this list is well communicated and if someone needs to bring up a new priority or make a change in the order, we will get some notice.<br>
<br>The second step, triaging bugs, is going to require help from everyone familiar with their area of the code base. It is important that people who have a stake in getting a bug fixed take some initiative here to represent their most critical bugs and send your thoughts on priorities to Michael and Jim. I don't believe this is a one person job. Here are some suggestions:<br>
<br>* Ricardo and Wad have been prioritizing the wireless and mesh issues.<br>* Marco has led the sugar team bug priorities in the past (do you want to do that again?).<br>* Chris would probably be best one for gathering the power mgmt related issues.<br>
* Martin should represent server issues.<br>* Each developer or tester should think about what they feel are high priority issues (upgrade issues, touchpad issues, backup) and send your requests to Michael and Jim to make sure they get evaluated. <br>
<br>Bug triage is very time consuming, so I would ask that everyone chip in and Jim and Michael be responsible for understanding/prioritizing the trac items for the August release.<br><br>Use cases are being developed as we go along. For instance, we have some use cases for the network/mesh scenarios. We should put for requirements or use cases whenever a feature or bug fix is more complicated than something one person can implement in an afternoon (like the control panel), or if there is disagreement about what it is supposed to look like to the end user. <br>
<br>[Michael, I know you have a wiki page started for the August release. Can you put links to priorities, use cases, requirements, and trac filters associated with this release? Ideally we could have test cases and results linked there as well.]<br>
<br>Other thoughts?<br>Kim<br><br><br><br><div class="gmail_quote">On Sat, May 17, 2008 at 7:01 AM, Tomeu Vizoso <<a href="mailto:tomeu@tomeuvizoso.net">tomeu@tomeuvizoso.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<div class="Ih2E3d"><br>
On Tue, May 13, 2008 at 1:41 AM, Kim Quirk <<a href="mailto:kim@laptop.org">kim@laptop.org</a>> wrote:<br>
><br>
> A high level view of this process:<br>
> 1) Prioritize feature and bug fix requests from deployments, developers,<br>
> support, our sales/marketing group<br>
> 2) Triage bugs to determine which bugs are critical to fix to meet the<br>
> priorities<br>
> 3) Translate these requests into requirements, use cases, and trac items<br>
> (bug fixes or task items).<br>
<br>
</div>Any news on this?<br>
<br>
Thanks,<br>
<font color="#888888"><br>
Tomeu<br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<br>
Testing mailing list<br>
<a href="mailto:Testing@lists.laptop.org">Testing@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/testing" target="_blank">http://lists.laptop.org/listinfo/testing</a><br>
</div></div></blockquote></div><br>