Okay, enough looking back.
1.0 draws a line in the sand, but we're going to confidently stride over it now and take Gtk# to the next level. In the short term, this means continuing to improve our docs. I don't see much point in binding newer API versions until we've documented the ones that we already have. We've made amazing progress in this area over the last two weeks. I'd like to see us get to 100% doc coverage in the Glib, Pango, Atk, Gdk, Gtk, and Glade namespaces, in addition to everything but the GnomePrint apis in the Gnome namespace before we start binding any new API versions.
The API freeze that we have in place now for 1.0 still allows us to fix broken API bindings. We are also going take advantage of the nice Assembly versioning and GAC functionality of mono to allow the addition of missing API related to the 2.2 Platform and convenience overloads for methods. This gives us a fair amount of flexibility to continue to improve the 2.2 bindings for a while, without breaking existing code developed against Gtk# 1.0. As an app developer, sticking with 2.2 should not disappoint you too much, since using newer API locks your app out of the still enormous Gnome 2.2 installed base.
One thing that has resulted from the big docs push of the past two weeks is a nice backlog of bug reports. The doc pass is also serving as an audit. It makes sense to me to finish this audit and fix whatever problems it identifies before we start thinking about Gtk# 2.0 and the Gnome2.6 platform library versions.
Please keep those docs and bug reports coming.