From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31546] New: Bugzilla upgrade
Date: Mon, 25 Mar 2024 18:41:56 +0000 [thread overview]
Message-ID: <bug-31546-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31546
Bug ID: 31546
Summary: Bugzilla upgrade
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: mark at klomp dot org
Target Milestone: ---
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.
The reason the 5.0.4 branch is still active is because there was
complete reformatting of the source code and a database schema change.
So upgrading is a bit of a pain.
We should pick a branch/version we want to upgrade to.
See also https://www.bugzilla.org/blog/#upcoming-releases
And make sure all patches/extras we want (e.g. sitemaps, various patches
we picked up from e.g. gentoo) are also on that version.
When upgrading (and having to change the schema anyway) we might want to
look into using a separate mysql database (patchwork, bugzilla, mnogosearch
share the same atm).
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
*** Bug 31547 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-03-25 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 18:41 mark at klomp dot org [this message]
2024-03-25 19:56 ` [Bug Infrastructure/31546] " LpSolit at gmail dot com
2024-03-25 23:24 ` mark at klomp dot org
2024-03-26 11:52 ` LpSolit at gmail dot com
2024-03-26 22:12 ` [Bug Bugzilla/31546] " mark at klomp dot org
2024-03-26 22:28 ` mark at klomp dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31546-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).