Re: [Fresco-devel] M3 and onwards

Tobias Hunger wrote:
> I am wondering wether those two bugs listed on 
> http://issues.fresco.org/milestone1 are the only showstoppers for M3. What 
> about the print-bug?

Printing no longer crashes the server with no known side-effects.
Current printing bugs involve text handling (haw haw) and image handling 
  (non-identity matrix cases go horribly wrong.)

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

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.

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

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

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

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

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?

Nick Lewycky