It's February 2009, and this bug is finally triaged... Am I to expect a release candidate soon? Or am we waiting for Jaunty+1? Needless to say, the error is still very much present...
It's February 2009, and this bug is finally triaged...
Am I to expect a release candidate soon?
Or am we waiting for Jaunty+1?
Needless to say, the error is still very much present...