[Bug Infrastructure/31546] Bugzilla upgrade

["LpSolit at gmail dot com" <sourceware-bugzilla@sourceware.org>]

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

Frédéric Buclin <LpSolit at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |LpSolit at gmail dot com

--- Comment #2 from Frédéric Buclin <LpSolit at gmail dot com> ---
(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


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). 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. 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.


> 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 automatically 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.

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