[Bug Infrastructure/31546] Bugzilla upgrade

["LpSolit at gmail dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=31546

--- Comment #4 from Frédéric Buclin <LpSolit at gmail dot com> ---
(In reply to Mark Wielaard from comment #3)
> That is unfortunate. To be honest I had hoped 5.2 could become a common
> release people could upgrade to from 5.0.x while we waited for 6.0 to become
> ready.

This is the plan, you are right, but upstream developers are focused on 6.0,
and so the 5.2 development is very slow (6 commits only in the last 6 months),
see the commit log:

https://github.com/bugzilla/bugzilla/commits/5.2/


And even the harmony (aka 6.0) branch is not very active:

https://github.com/bugzilla/harmony/commits/main/

So it will indeed take a while till they are released as stable.



> We can use this bug to make sure all patches/features we need/want are in
> 6.0.
> Like the patches mentioned in this bug and things like the RH sitemap code.

If there are specific features you want, and if they are not too invasive, they
could easily be implemented with the current version of Sourceware Bugzilla.
Please file separate bugs using Product:sourceware Component:Bugzilla (not
Infrastructure) and I can look at them. One example which comes to mind is
inline history. See how I did it for Mageia Bugzilla, which is also running
5.0.4:

https://gitweb.mageia.org/web/bugs/commit/?id=8d9c748a5e694fb544c082128c9756a0ca702334

(Note that I managed to loose my old SSH key when I bought my new PC, and so I
can no longer access sourceware.org using ssh. Someone from overseers would
have to help me if you want me to help with Bugzilla.)



> That might take a bit. But if we want to help speed this up we could
> contract someone to do the work.

One problem is that upstream reviewers and approvers are pretty inactive these
days. So IMO the problem is more related to reviewing stuff than to submit
patches. There are many patches waiting for review, including security patches.

-- 
You are receiving this mail because:
You are the assignee for the bug.