Re: [Fresco-devel] M3 and onwards

On Fri, Sep 20, 2002 at 05:34:10PM -0400, Stefan Seefeld wrote:
> Nick Lewycky wrote:
> >Tobias Hunger wrote:
> 
> >>What should we aim for after M3? I'd love to see (a|nathaniel's) test 
> >>framework in M4. Anything else? We shouldn't add too much to our 
> >>plate: I don't want years to pass till we can get the next release out.
> 
> ok, create a task to set up a testing framework. That's one thing, and 
> it is totally unrelated to any milestones. Then let's create M4 etc. and 
> discuss what we can reasonably aim for.

Actually, that task already exists -- task30 :-).

> >I wouldn't be too upset if it took another one and a quarter years to 
> >come out, just so long as most of the issues we've been talking about 
> >putting off have been resolved.
> 
> I disagree. The current situation is really a pita. We should release
> much more often, may be twice a year. In fact, I hope that the issue
> tracker will allow us to track bugs and task at a level of granularity
> that makes releases at such a frequency possible.

AOL.

> >There's a bunch of design issues I want to take care of. We should 
> >prioritize these against the issues they're blocking. (Traversal 
> >architecture blocks work on a client-side scene graph generator.)
> 
> again, file those bugs / tasks, and specify their dependencies. Then
> let's sit down and define goals for the next milestones.

The proposed changes to the traversal are going to have to be hashed
out a lot -- I look forward to discussions :-)

[snip]

> >Postscriptum, I was just noticing that the link to milestone three is 
> >i.f.o/milestone1 . That's counterintuitive, even if it is out first 
> >milestone. Could we please bump the number, somehow?
> 
> no, please don't start thinking of the issue id as anything but an id.
> If we delete an issue that id becomes available anew...

Actually, I agree with Nicholas.  Those ids are very useful outside of
the database -- already I've gotten in the habit of referring to
"bug21" and the like, and they work with the web interface and
everything.  It's very confusing, then, that "M3" and "milestone1" are
the same thing.

And we shouldn't be deleting issues... even if we did in some special
case, it would just confuse things to reuse the id.

> Now let's finish M3. Please file *any* issues you find with the current
> snapshot (notably the 'server -R' stuff) so we can move.

Hrm, right, the -R stuff.  I'll try to find time this weekend to do
something about that, if I can...

-- Nathaniel

-- 
Details are all that matters; God dwells there, and you never get to
see Him if you don't struggle to get them right. -- Stephen Jay Gould

This email may be read aloud.