UVF vs. gtk-sharp2 2.3.90

Brandon Hale brandon at smarterits.com
Sun Aug 21 14:10:55 CDT 2005


There is a new upstream release of gtk-sharp (2.3.90) which reflects a
sizable ammount of bugfixing and stabilization work.  This release is
also finally endorsed by upstream as API stable.

I attempted in the time leading up to UVF to get a tentative timeline
for gtk-sharp2 release cycle, but was unable to get any sort of
commitments on this, other than the previously speculated dates would
slip.  I was pretty upset with this situation, but I eventually spoke
with mdz who didn't seem terribly concerned given that our targetted
apps are in good shape.

Impact on apps already in breezy:
Monodevelop (main) - Application itself is fine, needs a small fix to
redirect new project files to the correct gtk-sharp2 assemblies.
Muine (universe) - one line patch to fix a namespace conflict.
Cowbell (universe) - works as-is

What if we stay frozen?
If we stick with 1.9.5, all of our currently shipped apps will continue
to work reasonably well.

Power users and developers will probably end up replacing gtk-sharp2
with their own builds, backports, unofficial packages, as upstream
software developers look for the API stable release in configure.
Developers on Breezy may hit bugs in their apps that didn't crop up in
our targetted apps.
 
Future versions of apps may or not build cleanly or backport to the
shipped 1.9.5.  Upstreams (f-spot, beagle) are already quickly moving to
2.3.90. I am hoping to throw the next f-spot and beagle into universe
before preview time.

Thoughts? Questions?

Thanks,
Brandon Hale




More information about the ubuntu-devel mailing list