public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31546] Bugzilla upgrade
Date: Mon, 25 Mar 2024 23:24:01 +0000	[thread overview]
Message-ID: <bug-31546-14326-KKHZg556Wa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31546-14326@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Frédéric 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.
> 
> Sourceware and GCC Bugzilla are indeed very close. I did very minimal
> changes to both, see:
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=18330
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64968

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=108473

> Bugzilla versioning was not complicated... till new upstream managers
> managed 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
> 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 release
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.
> 
> > 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
> 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 contract
someone to do the work.

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

  parent reply	other threads:[~2024-03-25 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 18:41 [Bug Infrastructure/31546] New: " mark at klomp dot org
2024-03-25 19:56 ` [Bug Infrastructure/31546] " LpSolit at gmail dot com
2024-03-25 23:24 ` mark at klomp dot org [this message]
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-KKHZg556Wa@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).