To recap, bugzilla.gnome.org (henceforth bgo, of which I am nothing but an enthusiastic user) is running a rather heavily patched version of Bugzilla 2.x. One of the changes from 2.x is a system to let people set a patch’s status using a drop menu from any one of a number of options (including “obsolete”, “reviewed”, “rejected”, “committed”, “commit after freeze”, and so on), rather than simply the boolean “obsolete” or “not obsolete”.
In the meantime, Bugzilla 3.x has evolved a separate system of flags for greater control over a patch’s status, so that you can have a number of not-quite-boolean flags set on or off or maybe for each bug.
There is an idea, tracked as GNOME bug 433607, that bgo should switch to Bugzilla 3.x, which would be lovely and allow a lot more fun things such as XML querying of bugs, which is something I really want. Last year sometime in 433607 I said I would have a try at porting the bgo status system over to 3.x, and I’ve finally had time to do that over the last few days. Here’s the result.
However, I put this into Mozilla bug 431438 which was immediately marked as a duplicate of Mozilla bug 353690, which is saying that flags (in the 3.x sense) should be able to have arbitrary values. This won’t be released for another year until Bugzilla 4.x. So I suppose either we stick with 2.x, go to 3.x but apply the patch locally, go to 3.x and find a provable way to convert all existing statuses to 3.x flags, or wait for 4.x.
Lychee tea keeps me going!