Heads-up: string change in GNOME 3.22

Hi, I'm releasing a new version of libgnome-games-support 1.2 today. This is the active branch for both GNOME 3.22 and GNOME 3.24. It contains one translatable string change that was made in November, so no string break for 3.24, but it's a break for 3.22. The purpose of the change is to fix

Re: [glib][GDateTime] API and string freeze break request

On Mon, Feb 12, 2018 at 1:54 PM, Rafal Luzynski wrote: Thank you. So here I have the feedback from the i18n team, as Alexandre said I don't need an approval yet. What about any feedback from the documentation and release team? Maybe I don't need an approval as

Re: gnome-software string freeze break request

On Fri, Sep 14, 2018 at 8:08 AM, Matthias Clasen via release-team wrote: I asked for this, so +1 from me. +1 from me as well. You still need two translator approvals. ___ gnome-i18n mailing list gnome-i18n@gnome.org

Re: String Freeze Break - totem

"The source seems encrypted and can’t be read. Are you trying to play an encrypted DVD without libdvdcss?" It's challenging to come up with an error message that provides the right level of technical detail for users to be able to fix the problem, without confusing nontechnical users. Not

Re: [evolution-data-server] UI/string freeze break approval request

1 / 2 release team ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Seahorse - String freeze break

Oops! +1 / 2 release team ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Unauthorized translation changes in dconf-editor

On Sun, Mar 17, 2019 at 10:11 AM, Jeremy Bicha wrote: I am reviving this old thread because it looks like Arnaud never stopped making his changes. He has created separate "maintainer-only" branches. He makes his release tags and tarball releases from those branches. This has continued with the

Re: Unauthorized translation changes in dconf-editor

Please keep gnome-i18n@gnome.org CCed On Mon, Mar 18, 2019 at 5:02 AM, Arnaud Bonatti wrote: Hi Jeremy and Michael, hi release-team, 2019-03-17 17:01 UTC+01:00, mcatanz...@gnome.org : I see: https://gitlab.gnome.org/GNOME/dconf-editor/commits/maintainer-only-3-32/po which seems

Re: GNOME Music freeze break request

On Sat, Feb 16, 2019 at 9:02 PM, mcatanz...@gnome.org wrote: I like what Music is doing, +2. To be clear, that's 2/2 release team. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: GNOME Music freeze break request

On Fri, Feb 8, 2019 at 10:56 AM, Emmanuele Bassi via release-team wrote: Thank you for the clarification; in one of the issues you linked I saw the error screen with a GDBus blurb and I got worried. :-) On Fri, Feb 8, 2019 at 5:15 AM, Emmanuele Bassi via release-team wrote: Are we really

Doc team notifications of freeze breaks

Hi, Historically, our rules for freezes have required notifying gnome-doc-list@ of any freeze breaks. This rule has not always been followed (I'm a flagrant violator myself). Since nowadays documentation operates on a longer cadence (generally years rather than months), I think it really