From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CDE2A3858C36; Tue, 26 Mar 2024 11:52:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CDE2A3858C36 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711453935; bh=ThNva0yja02apJcKL0+ZrSQ/smomkEy56YB489OYqnE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=D5WtcdzTsiZ9103fPcetfiANlN1ijqY8FZGavQf/vNykNpZfSVKE7k+B7Mrzt2W0d bV+hv+uC7ywofS1iNynor2XknJjZ3KaP9hjA8PvUUZSbHlMRUIso75NaYRHvWt3Iab XFSbEfTCQEAipNaLMBReazskrHGoNIAzI4ENY4F8= From: "LpSolit at gmail dot com" To: overseers@sourceware.org Subject: [Bug Infrastructure/31546] Bugzilla upgrade Date: Tue, 26 Mar 2024 11:52:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: LpSolit at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31546 --- Comment #4 from Fr=C3=A9d=C3=A9ric Buclin --- (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 bec= ome > 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 month= s), 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 cod= e. 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=3D8d9c748a5e694fb544c082128c9= 756a0ca702334 (Note that I managed to loose my old SSH key when I bought my new PC, and s= o 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 th= ese days. So IMO the problem is more related to reviewing stuff than to submit patches. There are many patches waiting for review, including security patc= hes. --=20 You are receiving this mail because: You are the assignee for the bug.=