Hi Kendy,
Jan Holesovsky wrote (03-05-11 11:17)
Please - what went wrong that this serious bug has not appeared among
the 3.4 Most Annoying Bugs? Without that, it was impossible to focus on
this - it just stayed hidden among the flow of the other 'normal' bugs.
I guess it's partly my fault, cause I expected the problem to be picked
up, cause it was mentioned on some lists long ago. A bit naive, but
attracting in times of large work loads :-)
And please, do you have suggestions what can we do to stress / get to
the public knowledge that:
- to get the proper attention to the real blockers, they _must_ appear
in the Most Annoying Bugs
[https://bugs.freedesktop.org/show_bug.cgi?id=35673]
- the Most Annoying Bugs are meant for really serious bugs only, and not
for "my favorite red button should be blue", and that such bugs will be
removed from there
- daily builds [http://dev-builds.libreoffice.org/] are important, and
can be used for testing even between betas, ie. the next day after the
bug is fixed, and pushed to the repository
AFAIAC, I mention those regularly on the Dutch lists.
We need time to get this in the minds (and hearts) of the people.
Kind regards,
Cor
--
- http://nl.libreoffice.org
- giving openoffice.org its foundation :: The Document Foundation -
Context
(message not available)
- (message not available)
- (message not available)
- Re: [Libreoffice] [libreoffice-l10n] Re: REMINDER: Release 3.4.0-rc1 from ooo-build-3-2-1 branch == string and UI freeze · Cor Nouws
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.