Testing People, Support People, Technical Contacts in Deployments,<br><br>Please see the note below from Michael Stone who is the release manager for our upcoming 8.2.0 release. Along with Michael acting as a central contact point for development input to this release, Joe Feinstein has recently joined OLPC as our QA Lead. He will be generating the release criteria, and directing the test planning and execution. They are currently working to document the full list of features targeted for this release. Please send your thoughts on release criteria to Joe (copying appropriate public lists).<br>
<br>I have added a number of people to the TO: list who are technical contacts from various country deployments. We are talking about setting up a mailing list of deployment technical people (deployment-tech?). This list would be used for OLPC to post release and use-case information to countries. It can also be used for countries to provide feedback on requested features and serious bugs. Continue to use '<a href="mailto:help@laptop.org">help@laptop.org</a>' ticketing system to report bugs and get general help. Please respond if there is interest in this mailing list.<br>
<br>Thanks,<br>Kim Quirk<br>VP Software and Support<br><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Michael Stone</b> <<a href="mailto:michael@laptop.org">michael@laptop.org</a>><br>
Date: Thu, Jun 12, 2008 at 6:12 PM<br>Subject: Release Status Report - 8.2.0<br>To: <a href="mailto:devel@lists.laptop.org">devel@lists.laptop.org</a>, <a href="mailto:sugar@lists.laptop.org">sugar@lists.laptop.org</a><br>
Cc: Kim Quirk <<a href="mailto:kim.quirk@gmail.com">kim.quirk@gmail.com</a>><br><br><br>I promised regular status reports on our release work and I've been lax<br>
in writing them. Here are my current thoughts on the content of and<br>
risks associated with our second ("August") 2008 release, <a href="http://8.2.0." target="_blank">8.2.0.</a> These<br>
assesments are heavily based on current rates of improvement and<br>
available labor. (I'm seriously concerned about upcoming distractions,<br>
but don't quite know how to factor them in.)<br>
<br>
Current Thoughts:<br>
<br>
* I'm EXPECTING major changes in:<br>
<br>
a) Sugar frame/home-view rework - Marco<br>
b) Sugar control panel - Simon<br>
c) Browser improvements - Simon/Tomeu<br>
d) F-9 Rebase - Dennis/Michael<br>
e) Manually enabled power management - Chris/Scott/Deepak<br>
f) Presence & collaboration reliability bugfixing<br>
- Collabora, Morgan<br>
g) Backup to XS<br>
<br>
* I'm NOT EXPECTING major changes in<br>
<br>
the Journal<br>
the Datastore<br>
activity isolation (modulo faster launching)<br>
the neighborhood view<br>
<br>
* I'm UNCERTAIN about what architectural changes will be available for<br>
consideration in:<br>
<br>
collaboration (e.g. gadget, cerebro, telepathy-cerebro).<br>
- Collabora, Polychronis<br>
theft deterrence - Scott, Emiliano<br>
software provisioning (e.g. olpc-update / reflash) - Scott, Mitch<br>
wireless/connectivity - Michailis, Cozybit, Deepak<br>
<br>
I'm also UNCERTAIN about several CONFIGURATION DEFAULTS like:<br>
<br>
touchpad in absolute or relative mode?<br>
hot-corners delay?<br>
activity placement algorithm / view<br>
invalid browser certificate handling algorithm<br>
<br>
Next steps:<br>
<br>
If you're working on something where I'm expecting major change, then<br>
we should discuss moving your changes from development into an<br>
official test build for QA in the next week. I suggest contacting me<br>
by public email with your first proposal. Documentation in Trac bugs<br>
or wiki pages will be happily accepted.<br>
<br>
(If you think I've misjudged an changeset, please reply so that we can<br>
fix the issue.)<br>
<br>
Open Questions:<br>
<br>
* You want to make changes to the release candidates. What is your<br>
burden of proof (of quality/readiness) today? What will it be N weeks<br>
from now?<br>
<br>
* We managed to ship the Ship.1? release only after we agreed on the<br>
"WE ARE DONE WHEN: ..." list. What are the contents of the release<br>
checklist this time around? (Need to figure out how to involve the<br>
deployment tech leads... in answering this).<br>
<br>
<br>
Thanks,<br>
<br>
Michael<br>
<br>
<br>
P.S. - Ancillary documentation:<br>
<br>
Release Process: <a href="http://wiki.laptop.org/go/Plan_of_Record-2008" target="_blank">http://wiki.laptop.org/go/Plan_of_Record-2008</a><br>
Priorities: <a href="http://wiki.laptop.org/go/Priorities-2008" target="_blank">http://wiki.laptop.org/go/Priorities-2008</a><br>
<br>
Stub 8.1.1 Features: <a href="http://wiki.laptop.org/go/OLPC_8.1.1_Features" target="_blank">http://wiki.laptop.org/go/OLPC_8.1.1_Features</a><br>
(needs to be finished so we can write<br>
<br>
<a href="http://wiki.laptop.org/go/OLPC_8.2.0_Features" target="_blank">http://wiki.laptop.org/go/OLPC_8.2.0_Features</a><br>
<br>
for the QA dept).<br>
</div><br>