Re: [Fresco-devel] M3 and onwards

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.

> 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.

> 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.

>> A better texthandling would be nice too, but maybe only for M5? I 
>> think I should try to add a set of tasks to the tracker and then we 
>> can discuss which will go into which milestone.
> 
> 
> It's probable that you'll be getting FT2 font handling in the 
> GLDrawingKit for M4.

ok, file a task 'integrate FT support into the GLDrawingKit', assign
it to you, and make an estimate how long it will take you. Then we
can think about which milestone it will fit into.

> Also, the current unifont handling needs to go, since unifont is shipped 
> with a ->bdf converter and Freetype2 can read the resulting BDF file. (I 
> have a demo of FT2+SDL displaying that if you're interested, Hunger.)

that's very nice. That should probably go into M4 then.

>> Apropos discussing milestones: I would love to be able to do so via 
>> the tracker. I don't want/need to be able to edit the milestone 
>> itself, just add comments:-)
> 
> 
> Agreed. I'm not the release manager, but I'd like the opportunity to 
> bring up which bugs and tasks I feel should and shouldn't be release 
> blockers.

sure.

> 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...

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

Regards, and a wonderful weekend,
		Stefan