To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=8302
------- Additional comments from [EMAIL PROTECTED] Thu Aug 28 14:40:44 +0000 2008 ------- > @tanstaafl: you should get acquainted with the release schedule > (see http://wiki.services.openoffice.org/wiki/OOoRelease30 ) Ok... > before accusing, let alone insulting, anyone. I didn't 'accuse' or 'insult' anyone my friend - and I don't think I was even rude - I simply pointed out a somewhat painful fact. > Code freeze for OOo3.0 already passed some time ago Well, not *that* long ago... 4 months (April 2008), according to the link you provided. So... code freeze happened in April 2008, and the patch for this functionality was originally uploaded in May of *2007* - 9 *months* (almost a full *year*) before the code freeze, and 8 *months* before the feature freeze. Not only that, according to this thread, it was integrated in ooo-build in October of 2007, a full 6 *months* before the code freeze. So, how much time, exactly, do the devs need before merging a patch into the official build that has as many votes as this one has, *and* has a *working patch* that someone was willing to write to implement it? > and only show stoppers are being fixed now. Yes, this patch should had > been reviewed and maybe integrated earlier, but now it is too late for OOo3.0 Too late because the OOo devs are extremely unresponsive to user requests for features they (the devs) don't deem 'important', *even when a patch is provided*. This (the official OOo devs being slow and often unresponsive to accept patches from 'outside' devs) is a well known fact, and the primary reason that Novell started the go-ooo offering. Don't shoot the messenger... maybe your time would be better spent *listening*. I'm a *long* time OOo user - 7+ years in fact (we used Staroffice 5.2 before changing to a pre 1.0 version of Openoffice.org) - and Admin who rolls it out on all 60+ machines in our office - and I *do* appreciate very much the effort involved with developing and providing OOo - but there is also a very large level of frustration with OOo development (see above). --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- 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]
