Lior: “My name is Lior, and it has been 6 months since my last bug triage.”
Support group: “we love you Lior…”
While I was thinking of doing another openoffice.org bug triage for version 2.2.1, version 2.3.1 had already entered testing. Meaning the versions in testing/unstable are very similar. This also means users can easily test a fairly recent version of openoffice.org without running unstable…
So, I’m glad to announce the beginning of (my) 2nd openoffice.org bug triage. This triage targets 285 bugs out of 330 open oo.org bugs. The selected bug are ones which were reported against versions lower the 2.3.1 or have no version information at all.
The goal of the triage isn’t to close as much bugs as possible, but to get all the bugs updated with recent version. Hoping “not relevant any more” will be the answer for most pings. Last time about 1/3 of the bugs were reported as already fixed / not relevant any more.
For those of you who will get one of my pings, please don’t forget to send you current openoffice.org version info.
I know some of you don’t necessary agree with this method for closing bugs, as it allegedly puts the burden of testing and updating bug information on the users/reporter than upstream.
While I partially agree, I don’t see how can teams with so much bugs can handle all the bugs themselves without having someone doing a full time job on this issue (any volunteers ?).
People wish to review the progress of the triage (or even help…) can check the triage bugs list.
Seems I was too slow with this triage, version 2.4.0~rc1 is already in unstable…
It’s been only 4 moths since my last triage…