"Don Cox" <[EMAIL PROTECTED]> wrote:
> There is _no way_ of knowing how long it will take to fix a bug until
> you have fixed it, or what proportion of the bugs will prove to be
> difficult.
> There is nothing peculiar to Voyager in this. PageStream, for instance,
> is going through the same process. So are most programs.
Well, yes, there is - things like this ARE subjective - that's kind of Matt's point.
He was just asking what they meant by this 2/3 weeks - and you don't know either. You
don't know whether they are actually fixing bugs, doing testing, making cosmetic
changes, writing documentation, going on holiday, uploading the software over a VERY
slow link, making punch cards. Whether the 2/3 weeks is representative or achievable
or not depends entirely on what they're going to be doing during this time. Or they
might have been aiming to fix say 10 bugs but will put out a release anyway in 2/3
weeks time even if they've only fixed two of the bugs.
It's not therefore unfair to ask whether, in Chris' "expert" (in the sense that he's
closely involved and has the experience of these things) opinion what he thinks that's
likely to mean.
> I suggest you concentrate on asking some horses which of them is going to
> win next week's races.
That's really not the same thing, now is it?
For a start, all the other horses have quite a big say in which one will win.
In the case of Voyager development, the only people involved are Vapor. And
fate/chance/whatever, of course, but that's always there.
Come on, give Matt a break, he was only asking the question.
And Chris is quite able to answer anyway, it's not like everyone needs to jump in...
Rob
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
