|RE: [cross-project-issues-dev] DSDP-TM requests delaying our M6 dropby 4 days|
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Freitag, 04. April 2008 18:03
To: Cross project issues
Subject: Re: [cross-project-issues-dev] DSDP-TM requests delaying our M6 dropby 4 days
Lack of testing is no excuse for slipping dates ... as you can see from other typical eclipse project's behavior :)
My advise is to stick with the train metaphor ... if you leave the station late, you never know what other train you might run into later on, down the tracks.
While it does greatly depend on the wishes of your adopters and committers, I recommend you declare M6 with whatever you have, with whatever amount of testing you can do, but (as you've done here) warn people it hasn't gotten as much testing as you would have liked, due to the important API work, so if anyone runs into a blocking or critical issue, you would consider providing them with an M6b upon request.
Besides ... once one project slips, it'll change our mindset and you know who else will start asking for a slip too. :)
I think there can be good reasons to slip a schedule, but not so much for "unknown, potential problems" ... only for "we have a known problem that will prevent adoption of the milestone".
Back to the top