bugzilla.kernel.org migration tasks

[Konstantin Ryabitsev]

On Mon, Jan 16, 2023 at 08:12:23PM -0500, Dave Miller wrote:
> To clear up a couple misconceptions, 5.1 is abandoned in favor of 6.0, not
> 5.2.  If you're already running 5.1.x you will want to wait for one of the
> 5.9.x releases at a minimum before upgrading. Going to 5.2 will not be
> easily possible, since it's actually based on the 5.0 branch instead of 5.1.
> Maybe we need to renumber that branch as 5.3.x until we're ready to actually
> kill it off? You're not the first person to be confused by this.

Hm... I guess I was misreading your post [1] and understood that there is not
going to be a migration path from 5.1 to 6.0. However, I see that this is
spelled out much better in another post [2].

I'm happy to wait for a supported Harmony release and I'm also happy to
volunteer upgrade testing.

[1] https://bugzillaupdate.wordpress.com/2022/12/13/upcoming-releases-and-more-fun-stuff/
[2] https://github.com/bugzilla/harmony/blob/main/RELEASE_BLOCKERS.md

> As for your MySQL EOL problem, MariaDB is a drop-in replacement for MySQL,
> and is in fact, a fork of it, and continues to pick up most of the changes
> to upstream MySQL. However, MariaDB did not port the commit to MySQL that
> broke compatibility with Bugzilla (they thought it was a bad idea, because
> it broke a lot of other things besides Bugzilla, as well), so all newer
> versions of MariaDB work fine with Bugzilla.  If your maiin concern is
> security support for the database server, your easiest path there is to
> switch to MariaDB, which would require no changes to Bugzilla itself or its
> database.

Okay, let me run some tests -- we haven't tried MariaDB, because we assumed it
would have the same problems as newer MySQL. Thank you for the pointer.

-K