[6078] in Release_7.7_team
Minutes: November 5, 2008 Athena Release Team meeting.
daemon@ATHENA.MIT.EDU (Bill Cattey)
Wed Nov 5 17:04:28 2008
From: Bill Cattey <wdc@MIT.EDU>
To: release-team@mit.edu
X-Spam-Flag: NO
X-Spam-Flag: NO
X-Spam-Score: 0.00
X-Spam-Score: -5
Content-Type: text/plain
Date: Wed, 05 Nov 2008 18:05:14 -0500
Message-Id: <1225926314.2950.100.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Minutes: Athena Release Team meeting Wednesday November 5, 2008
Agenda:
1. Decision on 6 month vs. LTS Ubuntu Cycle.
2. Decision on whether we put 3rd party software in a separate
metapackage or to incorporate it into the existing
debathena-cluster-software metapackage.
3. Check-in on Athena 10 task status.
Includes jdreed documentation update.
4. Monthly Progress report.
5. Set agenda for November 19 meeting.
6. Other
Actions/Decisions:
1. Decision on 6 month vs. LTS Ubuntu Cycle.
Decided: Yes, we're going to try and go with this:
Ubuntu x.10 release for Athena in January
Ubuntu x.4 release for Athena over the Summer.
We will finish Athena 10 under 8.04, and attempt to go to 8.10 for
January.
We have a wild guess that it's about 60 man-hours to integrate a new
Ubuntu release. We hope and expect the lion's share of this to
come from Volunteers.
2. Decision on whether we put 3rd party software in a separate
metapackage or to incorporate it into the existing
debathena-cluster-software metapackage.
Decided: Alex Prengel will maintain a debathena-cluster-thirdparty
metapackage. We'll show him how to do this, and will leave as a future
implementation detail whether or not that metapackage will be
subdivided, for example debathena-cluster-math.
3. Check-in on Athena 10 task status.
Includes jdreed documentation update.
In the Monthly Status Report, we marked off the completed tasks and
created new goals around the open issues.
4. Monthly Progress report.
Done. Sent under separate cover.
5. Set agenda for November 19 meeting:
Agenda for next meeting which will be November 19 in W92-106A
1. Review Athena 10 status and gap to go-live.
2. Discuss Athena 10 documentation, specifically printer
support.
3. Discuss Firefox 3 for Athena 9.4.
4. Discuss Post-term Patch release, specifically Screen power
saving.
5. Update on Solaris Sunset effort.
6. Other
6. Other:
Athena Release Team strongly advocates that Owls pick up the Solaris
Sunset project to make sure customers understand that Desktop Athena
Solaris is going away in the next renewal cycle.
Release team will pick up work on the Monitor Shutdown support, and on
meeting Hotline's needs for system monitoring.
jweiss action items:
1. Check in with ops on issue of desktop/server platform split.
2. Check in on need level for the WANBOOT/Athena 9.4 solaris
installer.
3. Investigate a Nagios-based Athena cluster monitor for Hotline team.
Additional Athena 10 related decisions:
(Athena 10 decisions listed here are gathered up into a narrow focused
message and sent to the Athena10 list.)
With regards to quickstations: Putting the counter up and keeping it
visible is the highest priority. An annoy-o-gram is desirable, but
social pressure can substitute for a 100% reliable annoy-o-gram.
Clarified how Athena 10 updates work:
Present system: Client cron job notices a patch release and takes it.
New system: Client cron job notices updates packages and installs
them.
A mirror we control will put updates on hold during the usual
blackout period between drop date and the end of exams.
(Specific updates can be hand-added.)
Systems installing debathena-workstation would use our mirror
and thereby be subject to the blackout dates.
Putting a package into debathena-cluster-thirdparty means it gets
installed from upstream "right now" and gets upstream updates.
Updates made by the debathena developers are brought over into the
Athena 10 build system by hand on a periodic basis, generally
driven by email notifications of debathena check-ins.
The autodebathenificator is currently offline because it wants Intrepid
support. amb and rbasch will look into getting it back up soon.
-Bill
----
Important: IS&T IT staff will *NEVER* ask you for your password, nor
will MIT send you email requesting your password information. Please
continue to ignore any email messages that claim to require you to
provide such information.
----
William Cattey
Linux Platform Coordinator
MIT Information Services & Technology
N42-040M, 617-253-0140, wdc@mit.edu
http://web.mit.edu/wdc/www/
