Hi Ariel,
> I was going there, but just wanted to wait until I was at home and see > if I could patch this and compile the module again. I have already done > that, and the service now is correctly implemented > (http://www.openoffice.org/issues/show_bug.cgi?id=87700 [1] ) I suggest changed the issue type from DEFECT to PATCH. This has the potential to speed up things. > [1] by the way, if there is a patch - or even if my patch is not good, > the developer will only need 15 minutes to fix the issue - is it > reasonable to wait for 3.x? If 3.0 is planned for Sept/Oct, 3.x means > 2009; not very promising, and I have seen this 3.x-targeting in several > other issues. Is it 3.0 already frozen? There are no clear and comprehensive guidelines for issue targeting. In general, 3.0 means: We cannot ship without this fix. 3.x means: We plan to do this somewhere between 3.0 and 4.0. "OOo Later" means: There are no resources allocated to this, and probably won't be in the forseeable future. This is pretty fuzzy, and different people tend to interpret this differently. In particular, the "cannot" for 3.0 is a moving target, as its definition depends on priorities. In my personal opinion, since developer support should be a major goal, an issues such as 87700 would be covered by this definition. However, for the moment I suggest assuming that the owner of the issue will take care of it in a timely manner, since, as you said, it's really a rather trivial fix. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
