[Banshee-List] 2.6.1 (was: Re: Release management, and stepping it up to 3)
- From: "Andres G. Aragoneses" <knocte gmail com>
- To: banshee-list gnome org
- Subject: [Banshee-List] 2.6.1 (was: Re: Release management, and stepping it up to 3)
- Date: Thu, 04 Apr 2013 20:50:56 +0100
On 28/03/13 11:20, Bertrand Lorentz wrote:
BTW, regarding 2.6.1, I would like to get on it a fix for a crasher that
happens when using Ubuntu 13.04 beta. The proper fix should maybe really be
in gtk-sharp, but the workaround in Banshee is trivial and I guess it's much
easier to convince the Ubuntu community to include an updated stable banshee
than to rush a gtk-sharp 2.12.x release (which may contain very little) in
13.04 final. So by saying this I'm suggesting to not release too late and
not release too early either (wait for this fix!), I'll share more details
at the end of the week.
Sure, I'll wait to hear from you before going ahead with 2.6.1. I
don't think it's going to happen before next week anyway.
Bertrand, given that you seemed to want more time to review the patch, I
left it in the bug:
https://bugzilla.gnome.org/show_bug.cgi?id=696111
Now, take in account that today I convinced Ryan to give us more time to
fix the problem in the binding, and he committed [1] a workaround in
glib master and the 2.36 branch, which will become 2.36.1 and is what
Ubuntu final will use, he told me. You could still apply the
workaround-patch anyway, just in case.
This problem is even more severe in the case of gtk3 branch, because it
affects more GInterface usage than in the master branch. Fortunately, I
think I've just found also a fix for upstream gtk-sharp, so I proposed a
pull-request:
https://github.com/mono/gtk-sharp/pull/60
Easiest way to test it is run the samples/treemodeldemo.exe in gtk-sharp.
We could do another 2.99.x release of gtk# to get more testing. If we're
happy with it after some time, I guess it would be desirable then to
backport the fix too to the 2.12 branch.
Cheers
[1]
https://git.gnome.org/browse/glib/commit/?h=glib-2-36&id=cf1285a4a473ec0f9b51b298b4ea9c4717cb1243
PS: Don't forget the other workaround for the gconf threading bug (patch
from kalev).
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]