Hi Frank,
On 01/25/07 14:46, Frank Schönheit - Sun Microsystems Germany wrote:
thank you for your comments. These new interfaces/services are community
contributions and still work in progress, they will be reviewed,
discussed and changed accordingly soon.
That makes no difference. I assume that somebody has mentored the
community member and we should follow our own guidelines for new types
always. Why starting with old style type definitions which have to be
changed later anyway.
I totally agree to Stefan and we should fix this asap.
I'd voite for "asap" being before release of 2.2. Releasing a version
with types we know we will change soon is Not Good (TM),
the other option would have been to reject the community contribution
since the contribution was explicitly meant for OOo 2.2, a later
integration was not an option for the contributer. How would you decide
in such a case ...
it will only
burden us with compatibility issues later (even if they're not
published, yet).
sorry, I cannot see any compatibility issues here. I assume you are not
aware that there currently isn't a fully implemented / announced /
supported smart tag *feature* in OOo?
Regards,
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
