[6318] in Release_7.7_team

home help back first fref pref prev next nref lref last post

reminder: Athena Release Team, Tuesday 21 April 1:30 in W91-250

daemon@ATHENA.MIT.EDU (William Cattey)
Fri Apr 17 15:45:31 2009

Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BC44021B-36CB-482C-8D32-0D461AAD9107@mit.edu>
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@MIT.EDU>
Date: Fri, 17 Apr 2009 15:45:18 -0400
To: release-team@mit.edu
X-Spam-Flag: NO
X-Spam-Score: 0.00

As per our plan two weeks ago, there will be a Release Team meeting.
The next meeting wil be Tuesday 21 April at 1:30 in W91-250.
(Remember also that Monday is a holiday so objects in calendar are   
closer than they appear.)

The tentative agenda from last time was:

  * Athena 10 Status review.
  * Metrics

Normally I list the questions and open tickets, but I've not had a  
chance to review that stuff.

The tactical thing Release Team needs to do is the bi-weekly status  
check-in.

The strategic thing Release Team needs to do is to plan for the  
transition relating to my departure.
(Is there anyone on release-team who has not heard that I've been  
among those layed off?)

Perhaps a good exercise that brings strategy and tactic together is  
this:  Could someone, either broder, amb, or jdreed please review the  
Top 10 Wiki page, the open tickets in Jira, trac, and testers, and  
come to the meeting with a list like the one I usually bring?

I suggest you three have a quick IM chat and then announce to the   
release-team list how this task will get done.

I suggest we drop the "Metrics" item until we understand how the old  
business will be sorted out.

Therefore, the agenda for the next meeting will be:

	1. Athena 10 Status check-in.
	2. Beginnings of planning the transition for Bill's departure.

I say "Beginnings" because there are many discussions that need to  
take place that simply haven't happened yet.  For example, we know  
there are people leaving, but we don't know details of the  
organizational review. Those details will inform Release Team of what  
further changes need to be made to its scope and mission.

See you Tuesday,

Bill



home help back first fref pref prev next nref lref last post