Sorry, but I can't support this.

Mono have a history for somewhat... unready... upstream releases, which
require extensive patching and testing before they're ready. 1.9.1 in
Intrepid already has 19 patches applied to it, and all of those would
require re-testing and re-auditing for 2.0 packages.

So close to Intrepid's release, I really don't think it's realistic to
put a MAJOR new upstream with a poor release quality history into the
default install of a stable version.

The pkg-mono team is actively working on Mono 2.0 for Debian, and I
think it would be foolish for Ubuntu to jump the gun with such a major,
major new release before it's been adequately tested and staged by the
active, cross-distro team at pkg-mono.

It'll definitely be in Jaunty though, and 2.0 packages for older
releases will appear in third party locations (such as my PPA) once
they're ready for human consumption.

-- 
Please update to Mono 2.0
https://bugs.launchpad.net/bugs/278946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to