Minutes of the GTK+ Team Meeting - 2009-10-20

[Emmanuele Bassi]

= minutes for the 2009-10-20 meeting =

1. schedule post 2.20 [bratsche]
 - aim for 3.0 after 2.20
 - list of things to deprecate, including signals and properties
 - figure out a diagnostic mode
 [discussion degenerates into pet features]
 - cross all items from the 3.0 readiness wiki page
ACTION: decide along with the GNOME 3.0 schedule

2. Git repository surgery [jjardon]
 - removal of the gtk-2.16 branch
 - rename of the gtk-2.90 branch to gtk-2-90
ACTION: desrt to operate

3. state of development branches for 2.20/2.90
 - see point 1, re: massive mess of suggestions
 - xi2 requires testing with complex applications before review
 - resolution independence requires a high-level story for configuration
   before reviewing the API changes and more testing with non-gtk
   applications using gtk API
 - extended layout should hopefully get a review
 - deprecation of [H|V] variants or orientable widgets still depends on
   overriding the default value for properties in sub-classes

4. GtkCurve, GtkNotebook tab packing, non-multihead-safe API deprecation
 - deprecation of GtkCurve is agreed
 - deprecation of packing property for GtkNotebook is agreed
 - maybe deprecation of GtkRuler?
 - non-multihead-safe API removal for 2.90 is still on the fence, given
   the changes in X land; remote use case might still apply

4. glib 2.90 branching
 - glib 2.24 minus deprecations equals 3.0?
 - general agreement (also at the Summit): not worth doing a 3.0
 - it really boils down to features getting traction

5. gobject-performance
ACTION: wait for alexl and try to get the work done before glib-next

6. miscellaneous
 - some stuff fell through the cracks
ACTION: next meeting in one week

next IRC meeting: 2009-10-27

ciao,
 Emmanuele.

_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@...
http://mail.gnome.org/mailman/listinfo/gtk-devel-list

[Alberto Ruiz-4]

2009/10/21 Emmanuele Bassi <ebassi@...>:
> = minutes for the 2009-10-20 meeting =
>
> 1. schedule post 2.20 [bratsche]
>  - aim for 3.0 after 2.20
>  - list of things to deprecate, including signals and properties
>  - figure out a diagnostic mode
>  [discussion degenerates into pet features]
>  - cross all items from the 3.0 readiness wiki page
> ACTION: decide along with the GNOME 3.0 schedule

First, thanks a lot ebassi for putting the minutes together and sorry
for not attending, the meeting clashed with some stuff I couldn't
quit, glad you're doing another meeting next week!

Regarding the list of things to deprecate, I'm wondering, if we
deprecate stuff post 2.20, does that mean that we're going to carry
with those deprecated symbols during the 3.0 cycle? My guess is that
anything that should be deprecated have to be deprecated for 2.20, so
that we can remove it? Or maybe I'm missing something here, please
clarify :-)

--
Un saludo,
Alberto Ruiz
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@...
http://mail.gnome.org/mailman/listinfo/gtk-devel-list

[Christian Dywan-3]

Am Wed, 21 Oct 2009 00:55:43 +0100
schrieb Alberto Ruiz <aruiz@...>:

> 2009/10/21 Emmanuele Bassi <ebassi@...>:
> > = minutes for the 2009-10-20 meeting =
> >
> > 1. schedule post 2.20 [bratsche]
> >  - aim for 3.0 after 2.20
> >  - list of things to deprecate, including signals and properties
> >  - figure out a diagnostic mode
> >  [discussion degenerates into pet features]
> >  - cross all items from the 3.0 readiness wiki page
> > ACTION: decide along with the GNOME 3.0 schedule
>
> First, thanks a lot ebassi for putting the minutes together and sorry
> for not attending, the meeting clashed with some stuff I couldn't
> quit, glad you're doing another meeting next week!
>
> Regarding the list of things to deprecate, I'm wondering, if we
> deprecate stuff post 2.20, does that mean that we're going to carry
> with those deprecated symbols during the 3.0 cycle? My guess is that
> anything that should be deprecated have to be deprecated for 2.20, so
> that we can remove it? Or maybe I'm missing something here, please
> clarify :-)

Yes, we need to deprecate in time for 2.20 if we want to remove
symbols, anything that comes later will survive 2.90. So if you can
think of specialized or rarely used API, please add it to the agenda
and/ or file a bug report.

ciao,
    Christian
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@...
http://mail.gnome.org/mailman/listinfo/gtk-devel-list

[Carlos Garnacho]

Hi!,

Thanks a lot for the minutes Emmanuele, I absent-mindlessly missed the
meeting...

On mié, 2009-10-21 at 00:29 +0100, Emmanuele Bassi wrote:

> = minutes for the 2009-10-20 meeting =
>
> 1. schedule post 2.20 [bratsche]
>  - aim for 3.0 after 2.20
>  - list of things to deprecate, including signals and properties
>  - figure out a diagnostic mode
>  [discussion degenerates into pet features]
>  - cross all items from the 3.0 readiness wiki page
> ACTION: decide along with the GNOME 3.0 schedule
>
> 2. Git repository surgery [jjardon]
>  - removal of the gtk-2.16 branch
>  - rename of the gtk-2.90 branch to gtk-2-90
> ACTION: desrt to operate
>
> 3. state of development branches for 2.20/2.90
>  - see point 1, re: massive mess of suggestions
>  - xi2 requires testing with complex applications before review

I've been already testing with gimp, inkscape and xournal, although
latest weeks I was unable to fully test things due to having my tablet
broken.

Besides that, what would be the proposed schedule to merge this? As I
wrote in l.g.o [1], some non-pure GTK+ apps are affected by not getting
core events anymore (emacs-gtk, metacity), so if we're planning to merge
in 2.x, there should be a switch to enable xi2 prior to
gdk_display_open(). For 2.90/3.x, I'd just enforce app developers to do
the right thing, and not messing GdkWindows with XEvents.

Cheers,
  Carlos

[1] http://live.gnome.org/GTK+/MPX

_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@...
http://mail.gnome.org/mailman/listinfo/gtk-devel-list