[6507] in Release_7.7_team
Minutes from 11/13 meeting
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Sat Nov 14 16:42:06 2009
Message-Id: <949F0A18-200D-42D2-93E7-7A99FE6B2296@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: "release-team@mit.edu" <release-team@mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sat, 14 Nov 2009 16:41:52 -0500
X-Spam-Flag: NO
X-Spam-Score: 0.00
Here's what I believe to be a reasonable summary of the meeting. If
it's inaccurate, please chime in sooner rather than later.
1) Discussion of Karmic work plan and 6 month release cycle.
We picked the 6 month cycle initially for several reasons:
- It syncs nicely with the Ubuntu cycle, giving us 2-3 months to test
a new release before deployment
- IAP and Summer are the best times to update the clusters
- Regardless of cluster deployments, SIPB will likely support the new
distribution shortly after release, and supporting two different
versions is harder on support.
What can we change?
- We can punt a release if necessary, and if we do it should be the .
10 release.
- We have committed to run a cluster environment and keep it
reasonably up to date, and as such must release a new version at least
annually or revisit our commitment to the community (which cannot be
done unilaterally)
- We could move our deployment as late as March and November if
necessary, but that's less than ideal because it means deploying a
version less than a month before a new one is released.
- Faculty have been unhappy with versions changing mid-term; perhaps
that can be mitigated with outreach
What is involved in prepping a new release?
- We don't really know -- we can't even provide a reasonable estimate,
because the work to date has not only been prepping Karmic, but also 3
additional one-time projects:
-- Exchange support ramp-up
-- Krb4 desupport effort
-- Athena 9 -> Debathena transition (developing the Debathena cluster
environment)
- After the Karmic release, we can re-examine the work to date and get
a better idea of how much effort was divided amongst these projects
- Ubuntu tends to cram a lot of new features into the release
preceding an LTS release, and as such more changes might be required
on our end. So Jaunty->Karmic sucks. Karmic->Lucid is likely to be
as easy as Intrepid->Jaunty.
Where do we stand on Karmic:
- We will stick with our original goal of having Karmic "done for
IAP", in reality this means Fri 1/22/10 for deployment the following
week.
- This means we change priorities:
-- mitmailutils and nmh are lower priority. mitmailutils can possibly
be outsourced to an enterprising student
-- gdm fixes (removing the user picker and restoring Session, Actions
and Kiosk functionality) are high priority and are assigned to rbasch
with a rough estimate of 3-6 days.
-- Updating the installer and PXE environment is assigned to amb with
a rough estimate of 2-4 days
-- Developing a release-upgrade method is assigned to amb with a rough
estimate of 2-4 days
-- Migrating our build infrastructure to OIS colo servers is assigned
to amb with a rough estimate of 0.5-1 days.
-- Total ISDA effort: rbasch: 3-6 days. amb: 4.5-9 days.
