Return of Mille Update

Return of Mille Update - Please Read

[ Follow Ups ] [ Post Followup ] [ Forum ]

Posted by Smurfette () (Ranked on Backgammon (Games.com) Ladder) on May 09, 2005 at 08:33:34:

Hi all:

This isn't great news, not at all what we were expecting, however, at least you'll know what's going on.

A lot of this reads like stereo assembly instructions to me, however, I advise writing to Atari, letting them know the interest in getting Mille back faster. Perhaps they would move up their estimated time for return.

D2000lands (Drew) (09:56 PM) :
I just got an update on Mille. It could be an additional six months to a year possibly.
D2000lands (Drew) (09:58 PM) :
The public message shows Rook will be the first game coded back into the new site, whenever it happens (3-6 months for the beginning of the coding, estimated)
D2000lands (Drew) (09:59 PM) :
Posted by Betatestadmin Administrator Atari Employee
There is a certain cost/benefit issue that arises between the public's need to know and the impact revealing each little shift in plan has on the longer term schedule. And yes, it is fluid and the "to do" list can change without warning. Let's say we have the following, and announce it to you all:

1. Fix A list bug 1
2. Fix A list bug 2
3. Fix B list bug 1
4. Fix C list bug 1 - 4
5. Fix D list bugs 1-8 and begin coding Rook

At the point we are on step 3, fix B bug 1, and announce "it's fixed" we could come in the next morning to 2 brand new A list bugs that were caused, unwittingly, but the B bug 1 fix. Let's say these 2 new A list bugs take days to fix. We're off schedule, we're dealing with a ton of posts and PM's and email about why we're not on step 4 yet...plus reports about the 2 new A list items, etc. It just spirals out of control trying to give detailed accountablity to the public on a project like this. We wouldn't do it for a retail disc based game, either, and those you pay for. What we can do is give rough ideas about where we are, where we plan to be, what's on the table (but not with a timetable exactly), what's at or near top of the list, so on. Honestly, it's about the best we can do with regard to information flow from us to you.

Follow Ups:

Re: Return of Mille Update - Please Read screampie 19:25:39 8/19/05 (0)
Re: Return of Mille Update - Please Read davex23 08:01:26 5/11/05 (0)
Re: Return of Mille Update - Please Read IcyIsis (Platinum) 19:57:12 5/10/05 (0)

Post a Followup

Ladder:
Ladder Name:
Password:
Password saved if checked

Subject:

Comments:
: Hi all: : This isn't great news, not at all what we were expecting, however, at least you'll know what's going on. : A lot of this reads like stereo assembly instructions to me, however, I advise writing to Atari, letting them know the interest in getting Mille back faster. Perhaps they would move up their estimated time for return. : : D2000lands (Drew) (09:56 PM) : : I just got an update on Mille. It could be an additional six months to a year possibly. : D2000lands (Drew) (09:58 PM) : : The public message shows Rook will be the first game coded back into the new site, whenever it happens (3-6 months for the beginning of the coding, estimated) : D2000lands (Drew) (09:59 PM) : : Posted by Betatestadmin Administrator Atari Employee : There is a certain cost/benefit issue that arises between the public's need to know and the impact revealing each little shift in plan has on the longer term schedule. And yes, it is fluid and the "to do" list can change without warning. Let's say we have the following, and announce it to you all: : 1. Fix A list bug 1 : 2. Fix A list bug 2 : 3. Fix B list bug 1 : 4. Fix C list bug 1 - 4 : 5. Fix D list bugs 1-8 and begin coding Rook : At the point we are on step 3, fix B bug 1, and announce "it's fixed" we could come in the next morning to 2 brand new A list bugs that were caused, unwittingly, but the B bug 1 fix. Let's say these 2 new A list bugs take days to fix. We're off schedule, we're dealing with a ton of posts and PM's and email about why we're not on step 4 yet...plus reports about the 2 new A list items, etc. It just spirals out of control trying to give detailed accountablity to the public on a project like this. We wouldn't do it for a retail disc based game, either, and those you pay for. What we can do is give rough ideas about where we are, where we plan to be, what's on the table (but not with a timetable exactly), what's at or near top of the list, so on. Honestly, it's about the best we can do with regard to information flow from us to you.

Optional Link URL:

Link Title:

Optional Image URL:

[ Follow Ups ] [ Post Followup ] [ Forum ]