Julian Foad wrote:
> We're still working on tree conflicts and I'm not confident that it's
> just one or two things left to do - we don't have a clear list of what's
> still needed.
>
> How can we best put some tight bounds on what's needed? Here's one idea:
> write out one use case from start to finish, and work it through with
> the present code, looking for problems where documenting a work-around
> is the most expedient way, and for where code fixes are essential. I'll
> start that.
That sounds like a good idea. Compartmentalizing tasks, and then getting the
low hanging fruit sounds very reasonable for a near branch date. For both tree
conflicts and other pending stuff, let's figure out what we can deliver here and
now, and then work on getting that stuff up to quality.
This may sound like a broken record at this point, but let's not repeat the 1.5
mistake of creating a release which had too much too late (and arguably too many
bugs).
-Hyrum
Received on 2008-10-30 20:09:03 CET