g-i freeze break

2019-03-08 Thread Christoph Reiter via release-team
Hey, Change in question: https://gitlab.gnome.org/GNOME/gobject-introspection/merge_requests/142 https://gitlab.gnome.org/GNOME/glib/merge_requests/711 fixes some annotation on the glib 2.60 stable branch. Since the annotations are handled through g-i we'd need to update g-i for this to take effe

Re: g-i freeze break

2019-03-08 Thread Andre Klapper
On Fri, 2019-03-08 at 09:19 +0100, Christoph Reiter wrote: > Change in question: > https://gitlab.gnome.org/GNOME/gobject-introspection/merge_requests/142 > > https://gitlab.gnome.org/GNOME/glib/merge_requests/711 fixes some annotation > on the glib 2.60 stable branch. Since the annotations are ha

3.33/3.34 schedule draft: questions

2019-03-08 Thread Andre Klapper
I've put up a draft schedule at https://wiki.gnome.org/ThreePointThirtythree and in https://gitlab.gnome.org/GNOME/releng/commit/6ff90169cc36f0793beaf27fde629cc7118eee6f Problem: GUADEC is very late (end of August) and 3.34 release should be in early September. On the other hand, anyone can branch

Freeze break request for mutter!486

2019-03-08 Thread Carlos Garnacho
Hi!, I figured better doing this here than over IRC... In the end several people agreed at #gnome-shell that https://gitlab.gnome.org/GNOME/mutter/merge_requests/486 may be a better fix for the swapped colors regression. Also accounting that there's been other reported issues around xwayland and d

Re: Freeze break request for mutter!486

2019-03-08 Thread mcatanzaro
+1 / 2 This new fix is more code, which triggers my "risky last-minute commit" instincts, but I trust you're proposing it because you think it's safer than the originally-accepted solution, in light of the "other reported issues." Michael ___ re

Re: g-i freeze break

2019-03-08 Thread mcatanzaro
On Fri, Mar 8, 2019 at 3:15 AM, Andre Klapper wrote: Yes please. r-t approval 1 of 2. andre 2 / 2, go for it. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Re: Freeze break request for mutter!486

2019-03-08 Thread Carlos Garnacho
Hey, On Fri, Mar 8, 2019 at 5:22 PM wrote: > > > +1 / 2 > > This new fix is more code, which triggers my "risky last-minute commit" > instincts, but I trust you're proposing it because you think it's safer > than the originally-accepted solution, in light of the "other reported > issues." Thanks

Re: 3.33/3.34 schedule draft: questions

2019-03-08 Thread mcatanzaro
On Fri, Mar 8, 2019 at 3:34 AM, Andre Klapper wrote: I've put up a draft schedule at https://wiki.gnome.org/ThreePointThirtythree and in https://gitlab.gnome.org/GNOME/releng/commit/6ff90169cc36f0793beaf27fde629cc7118eee6f Problem: GUADEC is very late (end of August) and 3.34 release should be

Freeze break request for GNOME Shell

2019-03-08 Thread Florian Müllner
Hey, I'd like to request a freeze break for a crash introduced by the fractional scaling support that landed in 3.31.92: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/450 The particular case in the bug report are "Foo-bar is now ready" notifications for windows with no .desktop file,

Re: Freeze break request for GNOME Shell

2019-03-08 Thread mcatanzaro
+1 / 2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

GNOME 2.32rc2 (2.31.92) RELEASED

2019-03-08 Thread Javier Jardón
Hi all! The second release candidate for 3.32 is here! Remember this is the end of this development cycle; enjoy it as fast as you can, the final release is scheduled next Wednesday! We remind you we are string frozen, no string changes may be made without confirmation from the l10n team (gnome-i