Whoops, sorry Tom and Ted, for some reason I parsed 'T' as 'Ted' instead of 'Tom'. Obviously I shouldn't write email without having at least one cup of coffee in my system. ;-)
Please ignore my previous response in its entirety. I'll try again...
On Sat, 22 Nov 2003, Bryce Harrington wrote:
On Sat, 22 Nov 2003, T Ingham wrote:
On Nov 22, 2003, at 2:04 PM, Bryce Harrington wrote:
Hi all,
Looking at the planned tasks for this release it seems we're quite close. Plus, a lot of work has been done, so I think the codebase is getting ripe for a release within a week or two.
For those working on things to go into 0.36, could you reply and let us know your status?
Thanks, Bryce
Lo',
I apologize for not being around lately, but I got a couple of new contracts and really want to make sure christmas is taken care of. Next week should be fairly light for me up till wed. ( at which point I'm driving to NY for 3 days )
Please let me know if there's anything I can help with mon/tues/wed.
-t
If you feel like doing work in the codebase, then fixing one or two of the issues Bulia identified are the best application of your effort. (Or fixing any bug in the bug tracker that looks critical.)
If you would rather focus on non-coding tasks, then helping with the verification and copying of Sodipodi bugs to the Inkscape tracker would help us get that task squared away.
While not required for 0.36, another highly beneficial task that will help us out in coming releases is to add explanations for various functions. Select a subdirectory or set of files in the codebase and for each function write a definition like this:
/** my_function(arg1, arg2) * * This routine blah blah... * On failure, the routine will yada yada... */ void my_function(int arg1, int arg2) ...
These comments will get picked up and parsed by Doxygen, and so will make the online documentation of the codebase useful.
I'm doing the above for sp-root.* and sp-path.* as part of my arrowhead work.
Bryce