[Libreoffice-qa] Bugzila 4.3.x versions cleanup

Joel Madero jmadero.dev at gmail.com
Mon Nov 30 07:59:50 PST 2015

Hi All,

> I agree with Tommy. Bugzilla is unfriendly enough. Shortening the list is a
> good idea.
> How many people report bugs which are specific to a given RC? Are there more
> than 10 people in the world doing this? 
> In fact at the pace the RCs are released it is nearly impossible for someone
> to test and report bugs specific for an RC... Even if TDF had people
> contracted to do this, they still wouldn't have the time to thoroughly test
> and report bugs in time to be fixed before the next RC (and even the final
> version) is released.
> In my opinion the all the alpha, beta and RC bugs should be grouped ta o
> single version as soon as the following final version is released 
> E.g. All 5.0.0 alpha, beta and RCs should be grouped into 5.0.0 when the
> first RC for 5.0.1 is announced to the public (and added to the list).
> In fact, at this point there should be only the alphas, betas and RCs for
> the 4.4.7, 5.0.3 and 5.1.0 releases (and it's quite enough confusion to have
> 3 branches releasing at the same time...)
The problem really is that at least *I* do often time request users to
go back and install older versions to help narrow down where a
regression was introduced. This is particularly useful when a user is
complaining about their regression not getting love - at this point I
start heavily suggesting they do some of the lifting themselves to move
it forward (bibisect themselves, if that's not possible to go back and
install older versions and try to narrow down to a beta/rc where the
issue was introduced). I've actually found this to not only be useful
for the particular bug but also useful in recruiting new people.


More information about the Libreoffice-qa mailing list