Hi,
Am Freitag, den 25.06.2010, 14:12 -0400 schrieb Colin Walters:
On Fri, Jun 25, 2010 at 12:50 PM, Matthias Clasen
matthias.cla...@gmail.com wrote:
Fwiw, a big motivation for all the sealing business was to make it
possible that GTK3 _can_ move faster and incorporate more new stuff
Am Fri, 25 Jun 2010 14:12:00 -0400
schrieb Colin Walters walt...@verbum.org:
On Fri, Jun 25, 2010 at 12:50 PM, Matthias Clasen
matthias.cla...@gmail.com wrote:
Sure, we could continue to shoehorn features in to 2.x and it will
increasingly get harder, and the bugs will increasingly get
Hi,
So I'm really concerned about what I see as the current GTK+ 3.0 plan,
which is to release a frozen 3.0 in August. At that point, we'll have
*two* ABI frozen libraries that are 92.3% the same. That's a really
unfortunate situation, especially since a good chunk of the features
that are
On Fri, 2010-06-25 at 11:28 -0400, Colin Walters wrote:
Hi,
So I'm really concerned about what I see as the current GTK+ 3.0 plan,
which is to release a frozen 3.0 in August. At that point, we'll have
*two* ABI frozen libraries that are 92.3% the same. That's a really
unfortunate
On Fri, Jun 25, 2010 at 11:28 AM, Colin Walters walt...@verbum.org wrote:
Hi,
So I'm really concerned about what I see as the current GTK+ 3.0 plan,
which is to release a frozen 3.0 in August. At that point, we'll have
*two* ABI frozen libraries that are 92.3% the same. That's a really
On Fri, Jun 25, 2010 at 12:50 PM, Matthias Clasen
matthias.cla...@gmail.com wrote:
Sure, we could continue to shoehorn features in to 2.x and it will
increasingly get harder, and the bugs will increasingly get harder to
fix.
What we need to *realistically* look at is what big features that
