[7202] in Release_7.7_team
Minutes from 12/10 Meeting
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Mon Dec 20 16:22:52 2010
From: Jonathan Reed <jdreed@MIT.EDU>
Content-Type: text/plain; charset=iso-8859-1
Date: Mon, 20 Dec 2010 16:22:45 -0500
Message-Id: <A2BB21F1-05B0-4EAE-8A85-AEA5F32BB6F9@mit.edu>
To: "release-team@MIT.EDU" <release-team@mit.edu>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Transfer-Encoding: 8bit
Our next meeting will be Jan 14.
1) Natty release
Do we want to commit to the release? We can either do this one, or wait until "P", which will be the next LTS. However, we'll still need to get "P" working, and since Natty is not right before an LTS, we don't expect it to suck too much.
People should install the Natty Alpha and see if anything looks like it will be a major stumbling block. December 30 is DebianImportFreeze, which means major APIs and similar things are unlikely to substantially before release.
We will reach out to SE (née ISDA) at the beginning of January to request development resources with a goal of having final project work identified by Jan 28 (last day of IAP).
Ubuntu Timeline: 2/24: FeatureFreeze; 3/24 BetaFreeze; 4/14 FinalFreeze; 4/21 Release Candidate; 4/28 Final Release.
Our Timeline: 5/6: Alpha. June 1: Beta. July 1: Early. August 1: Final.
For maximum awesomeness, note that all of Customer Support will be moving to E17/E19 on June 1 or 2.
2) Auto-update
Someone should verify that auto-update actually uses "getcluster" correct.
[ed. It does not. Ticket #753 opened.]
3) VMware offerings & NATs
Historically, Athena has not worked behind a NAT (and thus most VMs). At this point, we believe it's only Zephyr that will fail. However, someone should test it using VMware and/or a real NAT should test things. We should make this as VM-friendly as we can.
Random musings: Does the zephyr issue go away if we put the zephyr servers behind an F5? Or if we just have one zephyr server? [ed. Nobody is suggesting that those are actually good ideas]
4) Testers
We need additional testers for the Natty cycle. We should recruit some. Where should we advertise other than sipb? Jobslist? Where did SWRT used to advertise?
5) Rewrite homepage to force people to add them to release-announce
I've made a temporary change, but we need a complete redesign anyway. It's possible that the installer should also spam you about it.
6) Developer recruitment during IAP
Liz, Geoff and I are working on this.
