[Prev][Next][Index][Thread]

Re: 1.99o in July ??



>>>>> "Klaas" == Klaas Nebuhr <Klaas.Nebuhr@arbi.informatik.uni-oldenburg.de> writes:

    Klaas> Hi Cliff, you wrote :

    >>> (...) weekend.  The second is when 1.99o is out (hopefully
    >>> we'll get the remaining new functionality in 1.99o) and is
    >>> about a month away (i.e. mid July -- right before the
    >>> hackathon begins).
 
    Klaas>   Why estimating mid July. Let's say mid august. Everyone
    Klaas> would be happy to get it earlier. I already can hear it :
    Klaas> "1.99o is only two days away." or "gimme just another week
    Klaas> ...".  :)))

Heh.  Well, mid July is a bit of a hard date.  We will soon be
purchasing Cotton's plane tickets and that will finalize the hackathon
dates.  Any functionality that we don't get in place by then will have
to be seriously reviewed as to whether said functionality is worth
delaying 2.0 (Things that are worth delaying: NEXTSTEP port, minimal
System 7 support).

Before I worked for ARDI I used to use a very conservative way of
estimating how long it would take me to do things -- I'd multiply by
two and then shift into the next higher units (hours -> days, days ->
weeks, weeks -> months).  That gave me plenty of leeway and
consequently I almost always got things done way ahead of schedule.
However, back then I was a faster programmer and people had lower
expectations.  ARDI has done very well to raise people's expectations,
since we're currently doing today what many people said was impossible
only a couple of years ago.

    Klaas>   Yesterday I discovered a strange behaviour of 1.99m
    Klaas> (E/L). I like some music while working on the
    Klaas> computer. (i.e. testing E/L). So I used my cd-rom to play
    Klaas> some music with workman. When I started executor, it scans
    Klaas> for the cd-rom and (WHOOOOM) my cd started right from the
    Klaas> beginning to play.

    Klaas>   Maybe you should be more careful with scanning while a
    Klaas> device is busy.

OK, we've logged it as a non-critical bug that must be examined before
we ship 2.0.  That means that eventually we'll look at it and if
there's an easy fix it will be fixed for 2.0, if not, it will be
documented as a bug but not fixed until later.

	--Cliff



References: