Hi,
On 17.01.2014 15:33, Rob Weir wrote:
On Fri, Jan 17, 2014 at 4:34 AM, Oliver-Rainer Wittmann
<orwittm...@googlemail.com> wrote:
Hi,
during the review of issues (newly submitted ones and also critical ones) I
observed the following:
Sometimes it reveals that the described defect already occurs in OpenOffice
versions which had been released before OpenOffice found its new home at
Apache. Unfortunately, the available values for field "Version" in our
Bugzilla instance are limited to values of versions which had been released
under the hood of Apache.
In order to mark these kind of issues more accurate and to distinguish them
from issues which had been introduced in version 3.4.0 I propose to
introduce value "pre 3.4.0" (or similar) for field "Version" in Bugzilla.
From my point of view it will help - at least me - to prioritize the issues.
Any objections to introduce this new value for field "Version" in Bugzilla?
The thing we're trying to avoid, I think, is someone reporting an
issue in an older version of OOo without first upgrading and seeing
whether it is already fixed in the current version of AOO. If a bug
existed in, say, OOo 3.3.0 and still exists in AOO 4.0.1, it is not
incorrect to label it as an AOO 4.0.1 bug. In fact this will happen
quite often. We don't have the QA resources to do archeological
research and re-test every new bug in older versions.
So the meaning of "version" has been something like "what version of
the product did you detect the bug in" with the constriction that we
highly encourage the user to be running a current version of AOO
before reporting any bug.
This isn't a perfect solution, of course, and I have no objection to
us revisiting this. But I just wanted to make sure we all knew why it
is how it is today.
I can follow the arguments and I do not want to propose that every
reported issue should be checked in an older version.
But since OpenOffice found its new home at Apache we had changes at some
more basics - e.g. exchange of the neon library by the serf library,
more updates to 3rd party libraries, kick of Mozilla libs, introduction
of 3rd party library CoinMP, kick of STLport, introduction of the
Sidebar, introduction of IA2, removal of the "3-layer" office, ... These
changes might cause by side effects issues whose relation is not
directly seen. Thus, I personally draw more attention to issues which
had been introduced by 3.4.0 and later than to issues introduced by pre
3.4.0 versions. Thus, when an issue comes to my focus in an area which I
know and I am not aware of a corresponding change in this area since
3.3.0 which could have triggered this issue I have a former OOo version
at hand - OOo 3.2.0 and OOo 3.3.0 and also OOo 3.4 Beta. Thus, just a
quick check of the issue in these versions allows me to prioritize it.
Important is to keep this information searchable in Bugzilla. Thus, I
would like to tag issues which occurs in pre 3.4.0 version appropriately
and to filter these issues with corresponding Bugzilla queries.
Best regards, Oliver
Regards,
-Rob
Best regards, Oliver.
P.S.: Issue 123063 [1] is closely related to my proposal.
[1] https://issues.apache.org/ooo/show_bug.cgi?id=123063
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
