<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#ffffff"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Arial,'Lucida Grande',sans-serif; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 20px; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;">Meeting of the TB, 2010-05-18 <ul> <li>Chair: sabdfl</li> <li>Present: cjwatson, kees, keybuk, mdz, pitti, sabdfl</li> </ul> <ul> <li>Review of Actions <ul> <li>On Reinhard's patent question: pitti got a reply from Amanda [Canonical legal] and replied to Reinhard and tb@</li> <li>cjwatson has sync'd MoM</li> <li>pitti has switched Soyuz' sync-source.py</li> </ul> </li> <li class="gap" style="margin-top: 0.5em;">10.10.10 <ul> <li>The Board continued their discussion on the proposed release date for Maverick Meerkat. Concern was expressed about releasing on a Sunday: it was agreed that the release would need to be prepared by the previous Friday. Various stakeholders (webmaster, marketing) will be ready for the release on the Sunday, but the bulk of the work should wrap during the previous work week and only a skeleton team need be in place over the weekend, barring a release crisis.</li> <li class="gap" style="margin-top: 0.5em;"> The updated release schedule, with 10.10.10 has been published, and should now be considered canonical <img alt=":-)" src="cid:part1.09040501.09040707@ubuntu.com" title=":-)" style="border-width: 0px;" height="15" width="15"> </li> </ul> </li> <li class="gap" style="margin-top: 0.5em;">Releases to 12.04 <ul> <li>The Board discussed Robbie's data on the factors affecting actual development time during releases. It's now clear that April releases get reduced developer time, due to the number of Western holidays during the cycle. As a result, we would like to release the October release a little earlier than we have in the past.</li> <li class="gap" style="margin-top: 0.5em;">The Board voted and approved a proposal to ask Jorge Castro to engage with the GNOME release team, to see if they have similar dynamics in their cycle, and are amenable to aligning in this way. In addition, we asked Jorge to explore the possibility of publishing a schedule of release dates for 10.10 till 12.04, now. That would allow us to fix the dates of conferences, sprints and other events further in advance.</li> <li class="gap" style="margin-top: 0.5em;">The Board also discussed avoiding the final week of the month for releases, but the idea did not carry and no consensus emerged.</li> </ul> </li> <li class="gap" style="margin-top: 0.5em;">Sparc and IA64 Status <ul> <li> Keybuk pointed the Board at <a class="https" href="https://wiki.ubuntu.com/ArchitectureStatus" style="border-width: 0px; color: rgb(109, 76, 7);">https://wiki.ubuntu.com/ArchitectureStatus</a> which lists architectures and gives an indication of their degree of support in Ubuntu. </li> <li class="gap" style="margin-top: 0.5em;">The Board approved that Keybuk publicise that page, together with the statement that SPARC and IA64 are declining in levels of usage and maintenance to the point where they are candidates for decommissioning. In the case of SPARC, the issues are severe, with kernel and toolchain causing problems to the point of SPARC being unusable. In the case of IA64, there was some discussion of benefits to the team of having IA64 builds, and a recognition of the fact that kernel and toolchain are in better shape. Nevertheless, the decision was taken that unless a substantial community effort rallies around IA64, it should also be decommissioned, and Keybuk will frame the mail that way.</li> </ul> </li> <li class="gap" style="margin-top: 0.5em;">Derivative hosting requests <ul> <li>Persia asked if the TB needed to be involved in questions about new derivatives, and the decision was that yes, if the request involved hosting or modifications to key infrastructure and build services, then requests should be addressed by the TB.</li> </ul> </li> <li class="gap" style="margin-top: 0.5em;">The chair for the next TB will be Keybuk.</li> </ul> Thanks all, Mark </body> </html>