There is no mystery about it, we are totally off schedule. The last preview we published for Mageia 6 was Stabilization Snapshot 1 in June 2016, and Stabilization Snapshot 2 still hasn’t been published, although we have been saying “soon” for weeks, or even months! So what’s going on? Is Mageia dead? Fortunately not. But it’s good that you worry about it because it shows you like your Linux distribution. We need to communicate about the state of things so that you can stop worrying, so here we are.

For months we’ve been saying “the next ISO images will be published within a few weeks”… And that’s still how we see it… And actually lots of ISO images have been made, each one improving over the previous one, and Mageia 6 Stabilization Snapshot 2 will be very different from Stabilization Snapshot 1, because during all this time development has been going on, bugs have been fixed, packages have been updated, artwork has been integrated, etc. The good news is: Mageia 6 is really going to be good. And actually it already is, for all those who already run the packages from cauldron, the development branch. So why not release it now? Well, let’s try to give you some insight.

Summer 2016, the first troubles

After we released stabilization snapshot 1, we naturally went for the next one, although we knew that summer is usually family time for many contributors so that was likely to slow the release down a bit. Unfortunately, that was when one of our packagers, who was responsible for building the Live ISO images, but also worked as a sysadmin on our infrastructure and was of great help for debugging difficult kernel-related bugs, announced that he had to stop contributing for health reasons (he has come back since but had to lower his level of contributions). And we had not prepared ourselves for that so it took us time to get back on our feet. Fortunately, others stepped up to progressively fill this void, and we are now in good shape when it comes to ISO builders and the release team; they were responsible for Mageia 5.1, more on that later.

Independently of that, the number of release-blocker bugs had grown. Most of them belonged in the following categories:

Installer bugs.

Plasma 5 (successor of KDE 4) bugs, and there were many of them at the time because Plasma was still lacking maturity.

A nasty family of bugs where the X server (responsible for the graphical display) would fail to start at boot, giving only a “Good luck” message to the users. Many tried to understand what was going on, without success (until we finally cracked the problem!).

September to December 2016: new schedule and Mageia 5.1

Taking those difficulties into account, we changed the schedule, and decided to release Mageia 6 by the end of 2016, but certainly not later. (!)

Also, we felt that our users had already been waiting too long for the new release (so what should we be saying now!), so we decided that it would be nice to quickly build and release a Mageia 5.1 that would be Mageia 5 with all the updates that had been issued since its initial release. It would be possible to install it on newer hardware thanks to a newer kernel and drivers, and avoid the hassle of having to install loads of updates just after the installation. This was agreed upon at one condition: it should not delay Mageia 6 any further.

But…

That was when our servers chose to have severe hardware issues, and we were unable to build new ISO images (thus delaying the “build ISOs, have QA test them and report bugs, fix bugs, build new ISOs” process) for some time, and then other issues made it so that we could not build both Mageia 5.1 and Mageia 6 ISOs concurrently, as was initially planned. Remember: Mageia 5.1 was not supposed to delay Mageia 6. Well it did because of that. The making of Mageia 5.1, which we thought would be quick and easy, gave us more trouble than expected because of issues with the newer stable kernels (the same newer kernels that make it possible to install Mageia 5.1 on newer hardware).

Finally, we released Mageia 5.1. Phewww. We lost an additional two months on Mageia 6’s schedule.

Here we must clarify something: during the making of Mageia 5.1, only the ISO building team, some packagers, and the QA team were involved. The rest of the packagers, testers and developers still worked on Mageia 6, which got newer versions of Plasma – which allowed it to mature –, GNOME and other desktops, newer kernel, newer Xorg (which brought a nasty regression causing freezes when using Plasma or some other programs such as Chromium or VLC, but which we fortunately managed to help fix upstream in the Xorg project, and that benefited other distros affected by the same bug as well… That’s the free software spirit, we benefit from other peoples’ work, they benefit from ours), and many other newer things, fewer bugs too! The nasty “Good luck” bug was gone, the most annoying Plasma bugs were gone too (except one, still present these days, but we’re on it), several installer bugs were also gone.

We also had the opportunity to set up teams of maintainers for various critical parts of the distribution, something that most packagers and our triage team had been waiting a long time for. This brought the beginning of an answer to the situation where an important contributor stopping contributing for whatever reason would hinder us for a while. People joined the teams and we now have, for example, new people working on kernel packaging, installer development and bugfixing, and ISO building. All is not perfect but it’s moving in a good direction.

2017

In early 2017, the state of the distribution looked solid and QA was almost ready to let the Stabilization Snapshot 2 ISOs be released, thus putting an end to a looooooooong wait. Well, that was before they found a partitioning bug in the installer that was able to break your partition table. A broken partition table sadly means a more or less broken computer, unless you’re technically savvy enough to rebuild it correctly. Most of the time the easiest solution would be to wipe the entire disk (and lose data) and start again. The potential frequency of the bug was too high for us to allow the snapshot to be released to the wider public, even with Erratas and prominent warnings. You could be forgiven for thinking that fixing just one bug would be quick but since we’re all contributing over our free time, it actually takes time to 1) identify the issues 2) write patches 3) have the patches reviewed by another developer 4) build ISO images with the patches integrated 5) test them in various situations and on various hardware 6) find a regression related to the patch 7) write a new patch, etc.

It is not an agreeable situation and one of our priorities for Mageia 7 will be to work on critical paths so that we can solve problems faster without delaying the whole release process. Some of our contributors already kind of specialized in being the oil on the wheels for the rest of the teams, but we can do better (maybe with you?).

Disclaimer

The above history is incomplete, probably subjective (you can probably tell that it’s been written by someone who loves and believes in Mageia’s community), and can’t summarize everything that has been done by all the contributors in all the different teams. The author of this blog post thanks them all and is confident that most of you as readers are probably grateful to them too in spite of our lateness.

The current situation

The current situation is that we have a relatively good patchset to fix a number of installer issues, which have been committed to a testing branch and were successfully tested in pre-testing Live ISOs. Now we are deploying them on the full set of Live ISOs and classical installer ISOs for the QA team to test, which should hopefully be the final build for the Stabilization Snapshot 2.

As soon as we reach a satisfying solution for the partitioning bug, you will be able to resume testing the future Mageia 6. Then we will work as fast as we can to fix the last release-blocker bugs and release Mageia 6 to everybody.

You can help

If you love Mageia like we do and want to help us release it faster (while keeping our high quality standards), we would welcome you in one of our various teams of contributors: packaging, development, QA, ISO testing, communication (!) or any other of the diverse things we do. The contribution page is a good place to start, and you can hop on our IRC channels to discuss how you can help with other Mageia contributors.