main_trouble
Adept
i am loving my hardy amd64
hail ubuntu!
hail ubuntu!
main_trouble said:deluge is the most powerful(after azureus)
it is practically a utorrent clone
main_trouble said:deluge is the most powerful(after azureus)
it is practically a utorrent clone
Dark Star said:I have used Deluge but I was not impressed with it. Transmission provide gr8 spped . and when did I said that it is not available in Ubuntu :S
Gaurish said:What you miss in Deluge?
Ubuntu 8.04 demonstrates why strict schedules are undesirable
To witness the decline in quality that results from an uncompromising commitment to a time-based release cycle, one need look no further than the latest version of Ubuntu. Shuttleworth touts Ubuntu 8.04 as an example of smarter release management and argues that it demonstrates the Ubuntu developers' ability to adhere to a strict schedule.
"8.04 LTS represented a very significant step forward in our release management thinking. To the best of my knowledge there has never been an 'enterprise platform' release delivered exactly on schedule, to the day, in any proprietary or Linux OS," wrote Shuttleworth in a blog entry. "Not only did it prove that we could execute an LTS release in the standard six-month timeframe, but it showed that we could commit to such an LTS the cycle beforehand. Kudos to the technical decision-makers, the release managers, and the whole community who aligned our efforts with that goal."
Ubuntu 8.04, which was released last month, is a long-term support (LTS) release, which means that it will be supported on the desktop for three years and on the server for five years. From the start, Shuttleworth told users that quality and robustness would be the big focus for 8.04 and that it would be built to last. Unfortunately, it fell short of those expectations and shipped with a few serious bugs. The most frustrating problem that we noted in our review of Ubuntu 8.04 is the broken PulseAudio configuration, which harms both audio and video functionality.
A short delay would have made it possible to resolve problems of that nature before the release, but that never happened—perhaps because the commitment to releasing on time trumped the commitment to quality. Some might argue that a weak release is not a problem because bugs can be fixed in minor point updates after the initial release.
"Large deployments will wait for the first point release or two in any event," Shuttleworth points out in response to a comment on his blog. I suspect that I'm not the only one who thought of Microsoft's service packs after seeing that remark. But isn't the value of an official release that it provides some kind of quality guarantee? If releases are based on an arbitrary line in the chronological sand rather than completeness, they cease to have any meaning or relevance to end users.