Matthias B. wrote: > On Fri, Apr 3, 2009 at 8:51 AM, Juergen Schmidt <[email protected]> > wrote: >> First of all thanks for all the issue reports. 131 issues over which period? > > Our oldest issue is from May 17, 2005, so that would be almost exactly 4 > years. > >> You heavily use OO and of course the API. >> Probably for your use-cases every single reported bug was a showstopper. > > No. We can work around things that have never worked. It's the > regressions and incompatibilities that are the problem, because they > mean that a new OOo version fails where an old OOo version has worked. > This messes with our deployment and updating plans, because it either > forces an update of our extension on our customers or it prevents an > update of OOo. In an organization with several 1000 desktops managed > by 2 dozen independent IT departments, some of which are not exactly > fans of this whole MS Office -> OOo migration of which our extension > is a major part, this is a real bitch.
What about the following: Finding regressions early requires some test cases. We could need some help creating them. So if you have some APIs your application is relying on, could you write some Java test cases for them (let them do whatever you see fit) and contribute them to OOo? This would require that they can be used in our qadevooo-runner, but AFAIK that shouldn't be a problem. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[email protected]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
