Thank you Justin, On 2010-10-18 05:58, Justin B Rye wrote:
Filipus Klutiero wrote:It therefore allows users to easily access newer versions of packages; but users can not just upgrade to the following stable release but will at least need to also use the corresponding regular backport suite for packages from the sloppy suite. Woo - this sentence is heavy. I don't understand exactly what it means.Replaced with It therefore allows users to easily access newer versions of packages; but users can not just upgrade to the following stable release. They will at least need to upgrade to using the backports suite for the next release. (I hope that's right).
Hum, "upgrade to" what?
Here, I would recommend to either support that release-critical bugs were fixed by linking to such a statement or fixed RC bugs, or to remove that item, unless someone is willing to rewrite.Is it newsworthy if packages, even popular ones like the<a href="http://packages.debian.org/chromium-browser";>Chromium web browser</a>, get removed or added to Debian's testing branch? Debian Project Leader Stefano Zacchiroli<a href="http://upsilon.cc/~zack/blog/posts/2010/10/Debian_squeezes_Chromium_back_in/";>doesn't think so</a> and points out that Chromium is a good example for the non-newsworthiness of these things. It had been removed from Debian's testing branch, causing a media fuss and some criticism, as it appeared that Chromium would not be part of the next stable release. However, as the release critical bugs have been fixed, the package was allowed back again. Which is - according to Stefano - actually not newsworthy either. This is one strange news item. I'm not convinced this should be included, but supposing it is... I haven't seen a "media fuss" about this, in fact I wouldn't have noticed if it wasn't for Stefano's blog post. The only "media" coverage I can see, on LWN, actually goes beyond squeeze and even beyond Chromium, so I don't think that news item alone can be treated this way. In any case, I'm wondering which release-critical bugs were fixed.I'm not doing corrections for you where they're just a matter of opinion - at least, not without a suggested alternative text.
According to the<ahref="http://udd.debian.org/bugs.cgi";>bug-tracking web interface of the Ultimate Debian Database</a>, the upcoming release, Debian 6.0<q>Squeeze</q>, is currently affected by 327 release-critical bugs. Ignoring bugs which are easily solved or on the way to being solved, roughly speaking, about 130 release-critical bugs remain to be solved for the release to happen. The high number should currently be 277. Note that a space is missing in "ahref".One unjustified opinion, one problem that I don't see in my copy.
The space was added by zobel.As for the unjustified opinion... it's a matter of looking at UDD. The referenced blog post, dated October 15th, contains:
Affecting Squeeze:327
At this moment UDD says 271(!)