If it goes this way, feisty will be the worst release since birth of ubuntu. Too bad for it, but having a really stable system since beta release and such a rotten package a few day before release date could disgust a lot of people, thinking that even if it is a beta, ubuntu could be completely crappy software.

I personnaly decided to skip this release, and I think I will either stay with etch or move to archlinux, gentoo or any other distro.

Feisty for people like Greg should be a “no thank you”. For me too. And it is sad to say so.

Maybe BSD world will be more interesting to use than linux one in the next few months ?

Anyway, good luck to ubuntu users and developers.

I’m not entirely sure but I suspect that the criteria for putting an updated kernel into the archives during development is “it works for me”, perhaps this late they get wider testing inside the kernel team (~4 people) first.

For final release nearly every paid ubuntu developer, lots of the community developers and lots of the general community test the proposed release on lots of machines.

It’s also taken for granted that people using a ‘beta’ product should be aware of the risks.

I don’t really care about the particular problem occurring in a beta because that is the chance you take. It doesn’t happen often but it does happen often enough that if you beta test things for any length of time you will get bitten every now and then.

Apart from any QA lessons maybe the only other lesson on offer is user expectation management?

Perhaps the “Software updates correct errors, eliminate security vulnerabilities and provide new features.” text in Update Manager could be changed in beta versions.

Maybe something like:

“This is a development version of Ubuntu. Updates may introduce new errors as development continues.”

2) Use of stuff in beta is going to be a bumpy road.

3) Please, oh please, stop them from using the word “release” or even planning a date until they get the wireless back to the perfect functionality which was seen in 6.10. It has been horribly broken for WEP encryption. 6.10 had fall-out-of-bed functionality for wifi; 7.04 continues to be broken, and encrypted wifi is how many folks are going to be getting updates. It is the CD-ROM drive of this decade.

I will be a nit and point out that the release schedule has Kernel Freeze on APR-5 and Release Candidate on APR-12. Having a show-stopping kernel updated AFTER kernel freeze is a big mistake; it should never have made it past QA (how DOES that get past QA anyway…?). If the kernel was that botched that it needed to be updated, the schedule should have slipped to accommodate more/better testing.

That being said…
1. I booted to the previous kernel (let’s see anyone do that in Windows!)
2. I grabbed the updated kernel today and will try it later (still running on the previous right now)
3. HOORAY UBUNTU for turning around a fix in 18 HOURS!!! This is a key reason why I like Ubuntu.

I have just read the discussion at Launchpad which is filled with nonsenses, considering Feisty is “still” beta. Kernel bugs so close to release does not make me happy, but it is something you should expect. Fortunately, we have Ben to put things in place so efficiently (thanks Ben).

I do not have a cat, but not-yet-released software have kicked by dog some times… poor boy.

[1] … easy for an experienced Linux user which feels comfortable with the command line and device files.

Stop saying a product is beta when it is tagged a release candidate on its roadmap.

I will stop using ubuntu because this is the kind of rotten kernel which can make any ubuntu user sick.

After having used for 3 weeks feisty without any problems – this is the more stable beta I’ve ever used – I won’t use it anymore.

Debian Etch IS THE WAY to go now.