It's not reasonable to advice people to use a versions with known security vulnerabilities, see http://www.openoffice.org/security/bulletin.html
So you have two choices: a) Provide a 2.2.2 (or 2.2.1.1 ) including the security fix b) Fix most urgent issues in 2.3 and provide 2.3.1 soon. Since sending people back to older releases is not a nice solution, I prefer solution b. But of course people responsible for OOo release cycles/management might have an other opinion about this ;) BTW - beside the issue with the help files, I can't see why the solution should be specific to ES community... Malte. Alexandro Colorado wrote, On 10/07/07 09:58: > On Sun, 07 Oct 2007 02:48:11 -0500, Martin Hollmichel > <[EMAIL PROTECTED]> wrote: > >> Alexandro, >> >> before doing this, we should be aware at least of the most important >> issues the Spanish community is talking about, >> >> Martin > > * Math module is completely broken: issue 81789 > * OOoBase have multiple issues breaking older implementations of base > * Issues with Calc capitalization, is not correctly implemented > * XForms also has experienced many bugs on performance > * Help files are not completely localized (locale ES-specific) > > Basically the 2.3.0 version cannot be recomended for production and I > agree in the sense the version was rushed because of OOoCon. However the > new features are not yet stable on the codebase and break different parts. > >> Alexandro Colorado schrieb: >>> We are experiencing a lot of bugs and backlash with the new 2.3 release >>> of OpenOffice.org. I had experiencing a lot of bad feedback on 2.3 >>> specially the ammount of bugs and overal low quality of localization. >>> We are thinking on going back to the 2.2 version and doing a 'roll >>> back' on 2.3 release. >>> >>> We are aware of the issues we can cause to the overal feedback of what >>> is going wrong with this version, but since the ES community is not >>> very strong on bug reporting we think that this will be a relative >>> small loss. >>> >>> I would like to know the opinion of the rest of NLC and see if this has >>> also been experiencing across the rest of the communities. >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
