From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B32193858D3C; Mon, 25 Mar 2024 19:56:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B32193858D3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711396602; bh=3YZ2dBI1jai7WJpufqJUPxx428Prm6OA0M4Sp2kwKa4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qQpP8P+saqDawH2Hxzb428qgZYb1myAfIcIKweDSEV92V0vxwx/dE1Jah/+njuiR2 NMPb4dKdtDQvSQ21E3Lfxzhqfn6uO8049dVrXBMuwaTMBX1CxBCPIMuIZBPJ+G0AFD N0VD5Uq27FB9j8y48+0mkxQ8wp61LEpDgAxcycKc= From: "LpSolit at gmail dot com" To: overseers@sourceware.org Subject: [Bug Infrastructure/31546] Bugzilla upgrade Date: Mon, 25 Mar 2024 19:56:42 +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: bug_status cc 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 Fr=C3=A9d=C3=A9ric Buclin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING CC| |LpSolit at gmail dot com --- Comment #2 from Fr=C3=A9d=C3=A9ric Buclin --- (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. Sourceware and GCC Bugzilla are indeed very close. I did very minimal chang= es to both, see: https://sourceware.org/bugzilla/show_bug.cgi?id=3D18330 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D64968 Bugzilla versioning was not complicated... till new upstream managers manag= ed to mess everything after I left the Bugzilla project in 2016. 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 unaccept= able changes for a stable branch (I had a long discussion with the upstream proj= ect leader last year who fully agrees with me). And there is currently no other release you could upgrade to. Bugzilla 5.2 is not ready yet, and let be hon= est: nobody cares about this branch. 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. > We should pick a branch/version we want to upgrade to. There is currently no such branch/version, so I'm marking this bug as WAITI= NG, but you could as well close it as INVALID or WORKSFORME. > When upgrading (and having to change the schema anyway) It's common to have DB schema changes when upgrading from one major version= to the next. Nothing special here. The DB schema changes are made automaticall= y by checksetup.pl during the upgrade process. Nothing to worry about, as long as you don't upgrade to 5.0.5 or 5.0.6. --=20 You are receiving this mail because: You are the assignee for the bug.=