Getting started
- Meeting time, minutes and name convention decisions
The team agreed we would continue to meet on Thursdays at 11 in W92-199 and
would rotate taking minutes based on last name.
The team agreed to include Mac or Win in the subject line of all tsm
communications (internally) when sending email and when speaking, remember
to state TSM Mac or TSM Win.

- Mailing list: tsm-release@mit.edu  

Review roles
 - Deb Bowser
Consultant to Dave and Patrick, will create test plan and test matrix with
input and feedback from PRC's.
 - Atticus Gifford - installer writer to include customized readme's as
provided with team input.
 - Dave Kalenderian - PRC for Windows Platform, maintainer of win notebook
 - Alex Kozlov - Win platform coordinator; new to TSM; learning phase
 - Patrick Whitney - PRC for Mac platform, maintainer of mac notebook
 - Al Willis - Mac platform coordinator, will test and review documents
 - Karl Witt - help desk liaison; keep hd staff aware of progress and
timeline, coordinate hd testing and training as needed.
 - Esther Yanow - documentation liaison, keep publications team aware of
progress and timeline, create new documentation, send to team for review
 - others?

Discuss release criteria:  
The team will work on a decision making process as we go along, consisting
of common scenarios such as what would hold up the release go/no go(i.e.,
major bug vs. minor bug) and identify list of core items show stoppers vs,
non.  List in the notebooks and/or test plan.
Deb stated communications are key in any release effort.

Review Project Plan:
*Added training section to include
HD training (generic, introduce new gui) and other possibilities; no need to
be detailed or involved
MacParnters, WinPartners
Quick starts
*Added documentation section to include but not limited to:
Product front door, about TSM 5.4, new features, system requirements, known
issues how to obtain and related links.
Other communications:
Digitalk article
Is&t newsletter
*Added retirement/desupport section to project plan
 - to be discussed at a future meeting
*Added draft release announcement to delivery phase

Review 'release underway' announcement:
Dave will send to team for review.  
Team will send feedback to Dave by next Thursday, Jan 25
Once final by tsm-release, Dave will send to ist-comm with a firm deadline
Timeline to send will be after vendor release (end of Jan or early Feb)

Determine deliverables
- Documentation see above

- Windows and Mac installers
Atticus will get to work on betas currently available; expect release
candidate by end of the month.

Test phase:
 - create pool of testers from within the DLC's (i.e., tsm usergroup, steve
dowdy, vista release and others)once we have a final beta and our testing
had been concluded.
Deb will create a test plan and send to Dave and Patrick for review and will
include OS versions, upgrading and new installations; team decision to be
made with regard to upgrading TSM prior to OS upgrade or uninstall.  This
will be tested and decided within this team.
Deb will revive the old test form (matrix) and will review with Dave and
Patrick to see what else should be added and what format to use (currently
cgi script).
Stock answers will be crafted from findings during test phase.


Next steps:
Dave to send team announcement by Friday, Jan 19
Dave and Patrick to update project plan
Deb will draft test plan by next Wednesday, Jan 24
Atticus will create Mac/Win installers and notify team of their availability
Esther will create bare bones doc and send to team for review
Karl to inform HD of release project kick off and timeline
Al to send a list of go/no go scenarios based on past experience by Jan 26.
Esther to inform Kate/Carol of timeline and quick start possibility.
Deb to talk to Jon so he is aware and can coordinate effort with Dave with
regard to Vista communication.
A Linux release project will take place in March/April timeframe.  Bill
Cattey will be the PRC (with help from TSM team).

Next meeting:  February 1, 2007 11-12 in W92-199
Atticus is scheduled to be the minute taker.  In his absence, it will be the
next team member.