Voilà un certain temps que je n’ai plus donné de nouvelles concernant le développement de Bugzilla. Je vous propose donc de vous donner deux infos majeures:
- Tout d’abord, il est désormais possible de soutenir financièrement le projet Bugzilla grâce à cette page de dons. C’est tout nouveau, tout neuf, ça vient de sortir. L’idée est de se servir de cet argent pour financer certains travaux ou achats servant au projet lui-même (et non de se financer des vacances au soleil). Donc si vous souhaitez contribuer au projet Bugzilla mais que vous n’êtes ni un développeur, ni un beta-testeur, voilà une bonne idée d’apporter votre pierre à l’édifice.
- Concernant la sortie prochaine de Bugzilla3.2, sachez que la route est encore longue, mais nous progressons. Nous avons actuellement une douzaine de bugs marqués comme "bloqueurs" pour la sortie de Bugzilla 3.2, mais près de la moitié est en phase d’être résolue dans un délai relativement court. Cela ne veut pas dire que nous n’acceptons pas d’autres contributions. Le code n’est pas encore limité à cette liste et ne devrait pas l’être avant Noël, probablement. Donc si vous voulez voir quelque chose de particulier implémenté dans Bugzilla 3.2, il est temps de se manifester (notamment en écrivant des patches, pas des requêtes!). Notez qu’il y aura tout d’abord la sortie de Bugzilla 3.1.3, aux alentours de Nouvel-An, pour les développeurs principalement; cette version étant relativement instable. Suivra la sortie de Bugzilla 3.2 RC1 au début de l’an prochain et éventuellement 3.2 RC2 suivant la qualité et le retour de la RC1. Donc il reste plusieurs mois de développement avant de voir la sortie de Bugzilla 3.2. Cette sortie signifiera par ailleurs la fin du support de la version 2.20.x.
I didn’t give any new information about Bugzilla for a long time now. Here are two important ones:
- First of all, it’s now possible to make a donation to the Bugzilla project. This way to contribute is new and will help us to spend money on some Bugzilla-related works. So if you want to support Bugzilla but you are neither a developer nor a tester, here is a nice way to contribute!
- About the release of Bugzilla 3.2, we still have a lot of work to do, but we are doing good progress. There is currently a list of a dozen of blockers, and half of them are very close to being fixed.We still accept patches for bugs not being in this list as the code is not yet frozen. We will probably freeze around Christmas after what we will only accept bug fixes for Bugzilla 3.2. So if you want to see a new feature being implemented in 3.2, you have to hurry up. Note that we will first release Bugzilla 3.1.3, probably around New Year. This release will mainly be for developers as it will still be relatively unstable. Then, we will release Bugzilla 3.2 RC1 early next year and based on its quality and feedback, we will either release a second release candidate or Bugzilla 3.2 final. So there are several months left before the next stable release. This release will also mean the end of life of the Bugzilla 2.20.x branch.
So I finally decided to upgrade my Mandriva Linux 2007.1 installation to the new 2008.0 release. I expected the upgrade to be quick and painless, but it was the opposite. Not only the upgrade failed for some unknown reason, but before it started to fail, the "remaining time" field was displaying "07:03". I first thought "7 minutes and 3 seconds", but after an hour or so, I realized it meant "7 hours and 3 minutes". Arghhh!!! So I went back watching TV (fortunately, there were two episodes of NCIS at that time). While giving a quick look at my PC, I realized a message was displayed informing me it couldn’t install cryptsetup. WTF??? I first clicked "try again", but the same error came back. Of course, clicking "pass" didn’t help as many other RPMs couldn’t be installed, probably due to the missing RPM. So I rebooted the system, tried again, but now selecting as few packages as possible, to have at least a minimal installation to work with. Again unsuccessful, but now due to another missing RPM.
So I decided to do a fresh install instead of a 7 hours-long non-working upgrade. Selecting KDE as my default environment, it started installing RPMs again, now with a "remaining time" field of 1 hour only. *Much* better! Unfortunately, it was now complaining that it couldn’t install glibc (despite it installed cryptsetup successfully this time). Again another try, but now selecting as few RPMs as possible (avoiding KDE as it failed in my previous attempt). Same result: a package couldn’t be installed.
Fortunately, I have a dual boot and I started my Windows 2000 partition to download some additional ISO images. OpenSUSE 10.3, Fedora 8 Test 3, and Mandriva Linux 2008.0 mini (instead of the DVD ISO which I burnt for nothing as all my attempts above failed). I first wanted to test them in VirtualBox to decide which one to use to reinstall Linux, but they all failed at some point. Maybe Linux doesn’t like VirtualBox, or my system is so slow trying to run both Windows 2000 and Linux at the same time that it was in fact very slow, much slower than what I could accept. So I gave Mandriva another (and ultimate) chance and burnt the mini CD ISO. The UI let me choose between KDE, GNOME and IceWM. I selected KDE, but after the installation succeeded (finally!), I realized I was seeing IceWM. The reason was that KDE is not available on the mini CD ISO. So why letting me select it??
Well, I could at least configure rpmdrake to download missing packages from the web. But as usual, it first tries to get missing RPMs from your installation disk before downloading them, which is fine. But it was unable to find it! rpmdrake was indeed looking at /media/cdrom2, but this path was invalid. So I edited the path to look at /media/dvd but it was still ignoring my change, still asking for /media/cdrom2. So I edited /etc/fstab itself, and rpmdrake was now happy and could find /media/dvd.
I’m using Linux for 8 years now, among which 4-5 years using Mandrake/Mandriva. I always had problems installing a fresh new copy, and all upgrades failed as far as I can remember. I hoped this time the upgrade would work correctly. Sadness…
Now I understand why end-users still use Windows: it just works! Maybe Windows has many cons, but I never had any problem installing it. And I have never been so happy to have Windows 2000 still installed on my PC. I hesitated a few weeks ago to use the whole HD for Linux only, and keep Windows 2000 in a virtual box. But after this irritating and frustrating experience, I decided I would never do so. Windows 2000 will remain on my PC for a long time, despite I boot my system on Linux 99.9% of the time.
I could also tell you how Mandriva 2008.0 decided to ignore my SoundBlaster 4.1 sound card, falling back to the one installed on my motherboard, how it ate my menu bar, how it slowed down my web experience by waiting 10-15 seconds before starting loading any web page (the fix is to add "install ipv6 /bin/true" to /etc/modprobe.conf, so why not doing it by default?), etc… but I think you got the point.