Hi,
if we want OOo become easier to use and broader use, we need to handle this
issue too.
Frank already pointed to the process description ...
especially because OOo 2 is near.
But we already had the feature freeze for OOo 2.0. So it's muchg to late
for OOo 2.0 (but we knew that, when the process was started).
is there any actions for this issue so this issue have chance to go to OOo
2.x ?
Maybe one:
- get a team of developers to implement the feature
- get a qa team to verify implementation
- get a team of people who manage all affected pieces of OOo (such as
help, documentation, installation ...)
- setup a cws, implement, test, integrate ...
If you do this within a few weeks, there might be a chance to get it
into 2.0.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
