Comments on: Edgy Isn't Ready https://pthree.org/2006/09/09/edgy-isnt-ready/ Linux. GNU. Freedom. Thu, 11 Jan 2018 12:06:15 +0000 hourly 1 https://wordpress.org/?v=5.0-alpha-42199 By: Christer https://pthree.org/2006/09/09/edgy-isnt-ready/#comment-5438 Fri, 15 Sep 2006 22:11:05 +0000 http://www.pthree.org/2006/09/09/edgy-isnt-ready/#comment-5438 Knot 3 is available now 🙂 aren't you so tempted 🙂

Man I'm awful aren't I

]]>
By: Aaron https://pthree.org/2006/09/09/edgy-isnt-ready/#comment-4336 Sun, 10 Sep 2006 02:52:55 +0000 http://www.pthree.org/2006/09/09/edgy-isnt-ready/#comment-4336 John-

Edgy isn't ready. That's all. Why the need from you to come out swinging? I don't blame Ubuntu or the devs for the current state it's in. It just isn't ready. With only weeks before the final is scheduled to be released, it isn't ready. Edgy isn't ready. But I have to ask why you feel the urge to attack?

Tristan-

Yeah. I asked for it. No question there. However, I would've expected more stability, as the snapshot is always pulled from the latest Debian Sid (or is is Debian testing?). Then again, it could be my hardware, and the fact that I have more than enough software installed on this machine that caused the crash. At any event, I'm back to Dapper, and will probably stay there for a few weeks after the Egdy release.

]]>
By: Tristan Rhodes https://pthree.org/2006/09/09/edgy-isnt-ready/#comment-4290 Sat, 09 Sep 2006 17:02:57 +0000 http://www.pthree.org/2006/09/09/edgy-isnt-ready/#comment-4290 Aaron,

I am sorry to hear about your experience, but I think it is fair to say that you asked for it. Ubuntu has a completely transparent development process, which means that anyone can choose to run a development releases if they want to see what is being worked on, and possibly help with the testing of those changes.

The Knot releases should be considered Alpha quality. And Knot 2 is only the second Alpha release in a string of Alpha releases (probably around 8). After these Alphas have become more stable, then Ubuntu will release 2 or 3 Beta quality releases. After those Beta releases are tested by a wider audience, Ubuntu will release a few Release Candidates, which are more stable than the Betas.

The Release Candidates can be tested on personal machines by Linux-savvy users, but there is still some risk. Most likely there will only be small bugs at this point, having gone through the Alpha and Beta phases. However, important production systems should wait until the final release is ready before upgrading. If you want to be very safe, then wait a month after the official release so that millions of people test the system before you do.

I hope you don't fault Ubuntu for your bad experience. I am personally very excited about the future of Ubuntu, and I love watching how the Knots are developing. During the development of Dapper, I used a virtual machine to follow the development of the Alpha Flights. I really enjoyed seeing which packages were being updated, what the release notes were, and seeing how the GUI aspects changed right in front of my eyes.

This is open source at it's best.

Tristan Rhodes

]]>
By: jtaber https://pthree.org/2006/09/09/edgy-isnt-ready/#comment-4286 Sat, 09 Sep 2006 16:17:40 +0000 http://www.pthree.org/2006/09/09/edgy-isnt-ready/#comment-4286 What are you trying to prove with this post - that an early test release doesn't work well? Duh. Or that you committed the stupid sin of not paying attention to all the warning messages and putting this on a production machine. If the RC crashes then you might post something like this. Honestly, think twice - post once. Perhaps Ubuntu should go back to using simple "Test 1, Test 2" instead of fun names that might be giving people like you a sense of release stability.

]]>
By: Christer Edwards https://pthree.org/2006/09/09/edgy-isnt-ready/#comment-4278 Sat, 09 Sep 2006 14:44:49 +0000 http://www.pthree.org/2006/09/09/edgy-isnt-ready/#comment-4278 Sorry you had such a poor experience with it. I've been running it now for a few days & I'm enjoying it quite a bit. I'm reluctant to install it on my production laptop that I use for work, but my home desktop is worthy of the test.

Doesn't make sense that you would have so many broken packages yet mine runs fine considering we used the same update method. Ooh well..

]]>