We're down to 16 release-critical bugs to fix for Wheezy to be released. Testing should be unfrozen in a matter of days.
Anybody have an ETA for Jessie?
ciao,
jdk

! of my machines is setup as testing so when Jessie comes available it'll just roll right into it.

The last news bulletin contained a planned release date of 4/5th May.

Thanks Eddy & Randicus. Yes, I know we'll roll right into it. Although "roll" is a bit mild for a metaphor. "Avalanche" comes to mind. I maintain a few machines including some at my friend's shop which is an internet point so the info is useful to me. Given the rate that the critical bugs are being squashed, 4/5th May sounds about right.
ciao,
jdk

Why not freeze the other machines until you know that Jessie will work for you.

They are all in use, working machines. I have no /fear/doubts that Jessie will work for me just as every new Debian testing version has worked for me in the past.
jdk

Hi,

I don't run testing, but historically, running testing just after a stable release can be a little uncomfortable for some less experienced users and can come as a bit of a shock if they've not experienced the transition before. So, if anyone running testing doesn't want to deal with this they may do well to replace "testing" with "wheezy" in their sources.list for now.


For most it'll be fine, but I'll be amazed if we don't get at least a few questions here about "broken" systems from "testing" users just after the release.

Evo2.

Lenny to Squeeze, and Squeeze to Wheezy was relatively painless for me, at least.

I think the biggest problems come from users not carefully reading the messages from aptitude/apt-get. I've been bitten by broken packages, but of course the package manager warned me and I was just too lazy to read the output of what will be removed before hitting Y. It took once or twice to learn such a lesson and never happened again.

Aptitude presents various solutions, and of course don't forget the ever important response Q for quit, which will make no changes and make no further attempt to resolve conflicts/errors.

So true! If things start getting scary, or you just don't have the time at the moment to deal with things getting messy, just hit Q and wait a few days. Things may resolve themselves in that time.

Well, we won't have long to wait before we can all swap Jessie experiences. Personally, I'm looking forward to it. Being frozen is sooooooo boring.
jdk

How long after wheezy becomes stable willit take to get Jessie going , same day?

Yup. I believe that's the case. Within seconds!
jdk

Have fun with Jessie in those first few days. I'll be thinking of you guys and gals when I upgrade to a stable Wheezy.

wheezy has almost always been stable for me, the only difference between wheezy & squeeze was gnome2 to gnome3
, no real hiccups.
Also those of you who waited for squeeze to become stable, if you haven't played with gnome 3 then you will find it quite different. You'll either Love it or Hate it.

Isn't the new Testing a copy of Sid at the moment Wheezy moves out of Testing?

As contradictory it sounds, for me Testing often gives more problems than Sid. In Sid bugs are solved faster and you don't have to wait until fixes propagate down to Testing. It doesn't always help to read the apt messages. When facing an installation problem it is nice not to break unexpectedly, but it is awkward when some conflict or bug stops you from installing that package or upgrade you just need.

jlinkels