|
|
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fswiss\fprq2\fcharset0 Tahoma;}{\f2\fswiss\fcharset0 Tahoma;}{\f3\fswiss\fprq2\fcharset0 Arial;}{\f4\fnil\fcharset2 Symbol;}}{\colortbl ;\red0\green0\blue0;\red0\green128\blue0;\red128\green0\blue128;\red128\green0\blue0;}\viewkind4\uc1\pard\fi-1800\li1800\tx1800\cf1\b\f0\fs20 From:\b0\tab Nathan Cornillon (Exchange)\par\b Sent:\b0\tab Wednesday, November 17, 1999 2:55 PM\par\b To:\b0\tab Murthy Srinivas (Exchange); Michele Freed (Exchange); Alex Armanasu (Exchange)\par\b Cc:\b0\tab Chris Steck (Exchange)\par\b Subject:\b0\tab RE: Alpha Plan Open Issue\par\pard\li360\cf2\b Alpha Refresh Dates\par\b0\tab Dec 16\tab We will review the bugs we have to decide if we need to do a refresh Jan 17. \par\tab Jan 3\tab We will review the bugs we have to decide if we need to do a refresh Jan 17, if we haven't already decided to do so.\par\tab Jan 17\tab We migth be an Alpha refreshed based on the bugs we've recieved.\par\par\b Alpha Refresh Criteria:\par\b0 The bugs have to - \par\pard{\pntext\f4\'B7\tab}{\*\pn\pnlvlblt\pnf4\pnindent0{\pntxtb\'B7}}\fi-380\li740 be blocking bugs with no work around\par{\pntext\f4\'B7\tab}be reproducable\par\pard\li360\parIf we can't make a drop that is better in a meaningful way, we will wait until the Beta when we can.\par\pard\par\par\pard\li360\cf0\protect\fs24 \lang1024\f1\fs16 -----Original Message-----\par\protect0\pard\protect\fi-1440\li1800\tx1440\b From: \tab\b0 Murthy Srinivas (Exchange) \par\b Sent:\tab\b0 Wednesday, November 17, 1999 1:04 PM\par\b To:\tab\b0 Michele Freed (Exchange); Nathan Cornillon (Exchange); Alex Armanasu (Exchange)\par\b Cc:\tab\b0 Chris Steck (Exchange)\par\b Subject:\tab\b0 RE: Alpha Plan Open Issue\par\par\protect0\pard\protect\li360\cf3\lang1033\f0\fs20 Alex, Nathan and I discussed this last night. The decision to have drops (other than the scheduled Alpha, Beta etc) should be based on\par\protect0\pard\protect{\pntext\f4\'B7\tab}{\*\pn\pnlvlblt\pnf4\pnindent0{\pntxtb\'B7}}\fi-380\li740 feedback w.r.t tool\par{\pntext\f4\'B7\tab}how many blocking bugs they've found\par{\pntext\f4\'B7\tab}how we're planning on reproing and when we can fix the blocking bugs\par\protect0\pard\protect\li360\parWhile we don't want to do too many drops we also want to make sure we're being responsive to blocking customer issues. Alex and Nathan will figure out a "checkpoint date" to evaluate the data and we can decide then.\par\parAdditionally, we should make sure that even if we can't or don't make additional drops we do fix the major customer reported problems for Beta to demonstrate progress. May require revisiting the Beta date later.\par\par\parmurthys\par\par\par\par\protect0\pard\protect\li720\cf0\f2\fs24 \lang1024\f1\fs16 -----Original Message-----\par\protect0\pard\protect\fi-1440\li2160\tx1440\b From: \tab\b0 Michele Freed (Exchange) \par\b Sent:\tab\b0 Wednesday, November 17, 1999 12:45 PM\par\b To:\tab\b0 Nathan Cornillon (Exchange); Alex Armanasu (Exchange)\par\b Cc:\tab\b0 Murthy Srinivas (Exchange); Chris Steck (Exchange)\par\b Subject:\tab\b0 RE: Alpha Plan Open Issue\par\par\protect0\pard\protect\li720\cf4\lang1033\f2\fs20\parI agree that waiting until end of Feb is way to long..... but, doing a drop a week is way to much, both for us and the customer. The JDP are used to IDW drops, which until recently was much further apart. In general, monthly drops are sufficient. \par\parI assume the bugs will be fixed in the tool between now and January so it makes sense to do an alpha refresh then - December is a waste as so many folks will be Y2k crazy.\par\parWhy can't we make a drop in Jan?\par\par\parThanks\par\par\protect0\pard\protect\li1080\cf0\f3\fs24 \lang1024\f1\fs16 -----Original Message-----\par\protect0\pard\protect\fi-1440\li2520\tx1440\b From: \tab\b0 Nathan Cornillon (Exchange) \par\b Sent:\tab\b0 Tuesday, November 16, 1999 3:21 PM\par\b To:\tab\b0 Alex Armanasu (Exchange); Murthy Srinivas (Exchange); Michele Freed (Exchange); Chris Steck (Exchange)\par\b Subject:\tab\b0 Alpha Plan Open Issue\par\par\protect0\pard\protect\fi720\li1080\lang1033\f3\fs20 Today AlexArm and I (NathanC) reviewed the User State Migration Tool\rquote s alpha plan. The key unresolved issues arose in the Issues Resolution section. The plan says \ldblquote If needed, there will be a new drop as often as once a week to fix blocking issues.\rdblquote The open issue is: \b Should we have any drops between Alpha and Beta?\b0\parAlex felt we should have no drops until the Beta drop (currently estimated to be End of Feb.). After his explanation that time spent doing alpha drops is time lost to Odyssey features, I agreed the original statement was too often. However, we were unable to come to an agreement on if any drops should be done between the alpha and beta. JDPs want to use the alpha to see how it fits into their migration plans, and what they can gain from it. Blocking issues will come up making it impossible for them get an accurate gage of this. Being totally unresponsive for one quarter (Dec, Jan, Feb) doesn\rquote t seem good for customer relations. It also seems likely they will consider the tool, and their problems, unimportant to us. \parThe tool is trying to help them solve their user state migration issues so we can have more Windows 2000 Professional desktops up and running as fast as possible. It is important this tool is a success and helps ease this process. An additional drop Jan 17\super th\nosupersub (assuming beta drop is end of Feb) show the JDP we are responsive, and help them keep moving forward using our tool. Most of the time between the Alpha drop and Jan 17\super th\nosupersub is busy with the holidays, so the half a quarter shouldn\rquote t be too bad of a wait.\par\protect0\pard\protect\li1080\f0\par\protect0\pard\protect\fi-1800\li1800\tx1800\cf1\protect0\par}
|
