[Fresco-devel] What needs to be done for M2?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

Now that we have that nifty tracker, how will we use it for the upcomming M2 
cycle? Now that M1 is released (was it announced yet? Well, it is out and 
available at the new website on www.fresco.org) we should think about what we 
want to archive with M2 and how to go on about the release cycle.

I propose to add a couple of tasks to M2 and declare a feature freeze 
imediently after these are done. Then we can release after and bugs of high 
enough priority are solved.

For my part I'd like to see tasks
8 Write coding styleguide (that's nearly(?) done anyway)
9 Adopt coding standard for all files
30 Implement a unit test framework for Fresco
39 Integrate Babylon's tests (currently called examples) into test framework
      (needs to be done as part of task30 anyway)
40 Add a scenegraph debugging framework

Not much user visible stuff in that list... but it will help to form a much 
more stable basis for M3 which then should have a couple of user visible 
stuff in it IMHO.

What are your plans for M2? It would be nice if we could add messages to the 
milestones and discuss things in the tracker... but then the ML has more 
active listeners, maybe someone outside the usual crowd wants to comment:-)

- -- 
Gruss,
Tobias

- ------------------------------------------------------------
Tobias Hunger           The box said: 'Windows 95 or better'
[email protected]                      So I installed Linux.
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE93Y2Wv0FZW3NyoqURAgV9AJoCBnx3Llnwr0A5EcFTyfmpEhSLhACZAetp
vaDT9l3SWDH3LB6DKrexcr8=
=Er4I
-----END PGP SIGNATURE-----