The road to Monodevelop 2.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
monodevelop (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
monodevelop-boo (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
monodevelop-database (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
monodevelop-java (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: monodevelop
I'm starting this bug to help track Monodevelop 2.0.
At this moment in time, the current "stable" upstream release of Monodevelop is 1.0. This has been the release included in Ubuntu since Hardy, and it is rather rough around the edges, truth be told. The next major version, 2.0, has just released its first beta (2.0 beta 1, AKA 1.9.2) which is a significant improvement to usability compared to 1.0. Beta 1 is upstream's "feature freeze" release, with a second beta due on March 8th, and the final release due on March 24th, to address bugs.
It would be great to equip Jaunty with this great new release, rather than the anaemic 1.0 release we've been using for ages (through fear of random SVN snapshots), but it's possible (or even probable) that 1.9.2 will miss Jaunty FF by a few days, due to assorted other packaging commitments for the pkg-mono teams.
My Jaunty PPA contains a current pre-release test package, as well as a required bugfixed mono-addins package (https:/
Preliminary testing shows that this pre-release package is in good shape, although it won't be uploaded to Debian until *all* of MD2 has been prepared (plugins in different tarballs, currently only the Database plugin has not been updated yet - and some plugins will need to go through NEW).
I'm subscribing motu-release to this bug to help inform about developments, and possible to help provide background information should a formal FFe be needed for some or all of MD2. Please go ahead and test the current package, we're keen to hear about issues.
Changed in monodevelop: | |
status: | New → Confirmed |
<sistpoty|work> directhex: do you have an estimate how many packages will need to be touched to reach the end of the road?
[13:45:10] <directhex> sistpoty|work, beyond the mono-addins sync (which will help other things)? monodevelop itself plus five or six plugins
[13:45:44] <sistpoty|work> directhex: ah, k, so no effect on other packages besides these?
[13:45:59] <directhex> sistpoty|work, indeed. it's pretty self-contained