From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0F3FF3858D39; Mon, 25 Mar 2024 23:24:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0F3FF3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711409042; bh=uZnXoFKY9qTHmlwFLFmJmFp/e5cASNV+c/3HFxJSQ4I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=t8H/AcKQwBXc2zzWkU6kDDFHNLG8IxkmiyZdWIZldNkSu3gFk1EyYVLdcslJgCZK+ ybfoVxSexukQrOCAXOh3J4Sn3RMWky1hElAOwFYXRmnKfymN9UMiS2iflzaIecwWEn CFhfv/imzFlsmfiO1e7LyABqDQk8LFUenwRrjsw8= From: "mark at klomp dot org" To: overseers@sourceware.org Subject: [Bug Infrastructure/31546] Bugzilla upgrade Date: Mon, 25 Mar 2024 23:24:01 +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: mark at klomp dot org 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 #3 from Mark Wielaard --- (In reply to Fr=C3=A9d=C3=A9ric Buclin from comment #2) > (In reply to Mark Wielaard from comment #0) > > Bugzilla versioning is complicated. We are on the 5.0.4 branch. And > > sourceware.org and gcc.gnu.org have slightly different patches. But > > they are very close. We did pick up various patches from others. >=20 > Sourceware and GCC Bugzilla are indeed very close. I did very minimal > changes to both, see: >=20 > https://sourceware.org/bugzilla/show_bug.cgi?id=3D18330 > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D64968 Thanks for those references. There have also been some patches from gentoo (which sadly is on 5.0.6 so needed reformatting): https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108473 > Bugzilla versioning was not complicated... till new upstream managers > managed to mess everything after I left the Bugzilla project in 2016. >=20 > Sourceware and GCC Bugzilla are currently both based on 5.0.4 because this > version is very stable, and the 5.0 branch is still alive (for now). There > is no valid reason to upgrade to 5.0.5 or 5.0.6, because they contain > unacceptable changes for a stable branch (I had a long discussion with the > upstream project leader last year who fully agrees with me). Sadly some other organizations did "upgrade" (like gentoo), which does make sharing patches a bit of a pain :{ > And there is > currently no other release you could upgrade to. Bugzilla 5.2 is not ready > yet, and let be honest: nobody cares about this branch. That is unfortunate. To be honest I had hoped 5.2 could become a common rel= ease people could upgrade to from 5.0.x while we waited for 6.0 to become ready. > And we are far from > a stable Bugzilla 6.0 (its internal name is Harmony), which started as an > internal branch from Mozilla based on Bugzilla 4.4. There are many changes > and new features in Bugzilla 5.0 which have not yet been "backported" to = the > harmony branch and which must be implemented to fully support a 5.0 -> 6.0 > upgrade. >=20 > > We should pick a branch/version we want to upgrade to. >=20 > There is currently no such branch/version, so I'm marking this bug as > WAITING, but you could as well close it as INVALID or WORKSFORME. Lets keep it open. We will want to upgrade eventually. But from your analysis it seems we should wait till 6.0 is ready (which will take a while). 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. That might take a bit. But if we want to help speed this up we could contra= ct someone to do the work. --=20 You are receiving this mail because: You are the assignee for the bug.=