I just read Gerv’s article about people complaining that they get update notifications from Firefox every week or so. I agree there are moments when the updates come at a pretty high rate:
- Fx 3.6.12: Oct 27 (8 days after Fx 3.6.11)
- Fx 3.6.11: Oct 19 (1 month after Fx 3.6.10)
- Fx 3.6.10: Sep 15 (8 days after Fx 3.6.9)
- Fx 3.6.9: Sep 7 (1.5 month after Fx 3.6.8)
- Fx 3.6.8: Jul 23 (3 days after Fx 3.6.7)
- Fx 3.6.7: Jul 20 (3 weeks after Fx3.6.6)
- Fx 3.6.6: Jun 26 (4 days after Fx 3.6.4)
- Fx 3.6.5: (not released)
- Fx 3.6.4: Jun 22 (2.5 months after Fx 3.6.3)
- Fx 3.6.3: Apr 1 (10 days after Fx 3.6.2)
- Fx 3.6.2: Mar 22 (2.5 months after Fx 3.6)
- Fx 3.6.1: (not released)
- Fx 3.6: Jan 21
5 times this year, an update notification came less than 10 days after the previous one: 3.6.3, 3.6.6, 3.6.8, 3.6.10 and 3.6.12. It looks like Firefox is following the odd/even numbering schema, where odd numbers mean "unstable" (3.6.7, 3.6.9, 3.6.11) and even numbers mean "stable" (3.6, 3.6.6, 3.6.8, 3.6.10). :) More seriously, I can understand user complaints: once per week or twice per month is too much, I agree. Having Firefox automatically and silently download updates in the background and automatically and silently apply them on the next restart (to avoid notifications which irritate users so much) would be a big win. Users wouldn’t even notice that they got an updated version, and most users don’t care. For silent updates, don’t even display the release notes page on restart. These users really don’t care, believe me! (I can see how my family and my coworkers behave when they see such pages: WTF!? That’s not my usual home page. I don’t even know what they are talking about!). When Microsoft Windows installs some updates in the background, you don’t get a whole page telling you it did. 99% of us wouldn’t understand what they are talking about anyway if they are too technical, and 99% of us wouldn’t care if they are too generic.
Now, users must also understand why they get updates: because their system or application is vulnerable to some threat!They don’t get an update notification simply because someone found a typo in the preferences panel!! People like complaining about frequent updates, but they also like complaining that something goes wrong with their application or OS, despite an update with this problem fixed was available for weeks if not months. I think that comments such as "if i need an update i can look for it" or "If you can’t get it right the first time, give it up" are ridiculous. If the user pretends to be able to look for updates himself, then go edit your preferences and disable automatic updates, and stop complaining! If you don’t know how to configure this, then notifying you is the right way to go. Personally, I want Firefox to notify me for new updates, so I don’t remember whether the default configuration ("automatically download and install updates") notifies the user at all or not. If it doesn’t and doesn’t ask the user to restart his browser, then I don’t see what the problem is with frequent updates. If it does, then I agree this should be a really quiet mode, where the update is only installed on restart (or be able to apply the update immediately without requiring the browser to restart). If a user changed his preferences to get notifications and he gets notifications every week or so, then just change your preferences back to their default, and stop complaining. So the ball is in both the Firefox and the user camp.
It’s usually easier to make Bugzilla work with Apache, but IIS7 made things a lot easier than in previous versions, and it’s now pretty trivial to make it work with IIS too. The screenshots below are in french, but I guess you can understand what needs to be done.
Only two actions are needed, as shown above. Two new panels will be displayed:
That’s it! Bugzilla should work fine now. :)
Our latest stable release, Bugzilla 3.6.2, is now available in 10 languages: bg, cs, de, en, es-es, fr, ja, pl, pt-br, and zh-tw. No idea what happened to the russian team, which disappeared soon after 3.5.2. No idea either for the belarusian team, which stopped releasing new templates after 3.2.3. If you don’t want to install the l10n templates yourself, but you want to see how Bugzilla looks like in other languages, you can play with this test installation, which has all the available l10n templates installed.
For those who use GCC Bugzilla and Sources Bugzilla (sourceware.org), please note that they have both been upgraded to 3.6.2+ (Sources Bugzilla was running 2.17.5 two hours ago, haha).
From what I can see, I’m not even sure we will ever see a Mandriva Linux 2011.0 release:
Based on the uncertain future of Mandriva Linux, some old Mandriva employees and contributors decided to fork this distro:
I wonder if this new organization will manage to make Mageia a successful fork. I wonder if they will be able to compete against Fedora, Ubuntu or SUSE.
Open source is a strange world. When you think something is here to stay for long, you suddenly realize that money also plays a role. Isn’t it, OpenOffice (aka, Oracle killed it)? AOL killed Netscape, and Firefox and Thunderbird were born, and are today successful products. Oracle killed OpenOffice, and LibreOffice is born, but it still has to prove it will be a successful product. And what about Mageia, Mandriva’s new fork? I guess forking a Linux distro is a bit less trivial than forking a single application.
Did the open source world show its limits? Aren’t there too many distros/applications already? Being allowed and able to fork a tool, or develop your own is great, but isn’t the open source community duplicating and wasting its efforts again and again every time a new fork or tool appears? Is it one of the reasons why Linux and some free applications cannot compete against Windows and Mac, and their non-free applications?
It’s already hard enough to make the average user accept open source applications (think OpenOffice versus Microsoft Office, think Gimp versus Adobe Photoshop, think VLC versus Windows Media Player, think Linux versus Microsoft Windows, etc…), but it’s a lost mission when they keep being forked and renamed.