I should have made clear that other than these little annoyances, we love MonoDevelop. I certainly prefer using it within my standard Linux and OS X environments over figuring out what I need to click on in Visual Studio to get anything done.
Whether this matters or not will depend on the what your application is doing and how many users you have. For example, if your application is database bound or file system bound you wont likely notice much of a difference as the time you spend running CIL code or interpreted code is a small portion of your overall CPU consumption.
With Mono 2.8 we significantly improved Mono's web server scalability, but this will not matter if your application does not use or require more than a handful of CPUs. But is incredibly useful for people that are scaling servers under load.
How is your team keeping such a fast pace? Do you get a lot of assistance or documentation for Microsoft. Your rate of feature parity with the MS releases is impressive.
In addition, a big help was the fact that Microsoft open sourced large swats of code in this release (DLR, MWF, OData, LINQ, and a bunch more).
One surprise was that debugging is hard because Mono uses a different format for debugging symbols. This means we get tracebacks with no line numbers.
The second surprise is that we have to munge resulting executables with corflags.exe to force them to run in 32-bit mode on 64-bit boxes where there are library dependencies that keep them from being 64-bit clean.
We are trying to develop using MonoDevelop but there are some weird incompatibilities with the SQL Server client library. These are not insurmountable, but it has been a hassle.
The other hassle is that MonoDevelop is terribly slow. It does not appear to be able to do incremental compiles so any change to the project results in a recompile of the entire project.