Re: About the "About frogr" translation

[Mario Sanchez Prada <msanchez gnome org>]

Hi,

Apparently I had my IMAP folders + filters all messed up and I thought I didn't receive this email at all, 
and discussed this with Alexandre privately based on the ML archives... so summing up here the conclusion.

On 7/11/18 17:00, Alexandre Franke wrote:
> [...]
> > I've just pushed a commit to remove the application menu [1] in accordance to the "Application Menu 
> > Retirement" initiative [2], and as part of that change I modified the string "About" in the menu (now the 
> > hamburger menu) to be "About frogr", as those guidelines recommend... meaning that there are now a bunch 
> > of translations at 99% with that one string missing.
>
> That change is only supposed to happen for 3.32. It is fine to do it
> already in master, but no 3.30 release should be affected. You should
> have a gnome-3-30 branch that is not affected.

As clarified to Alexandre, frogr is not a core GNOME App and doesn't follow GNOME 6-month schedule, just a 
simpler "release when its ready" policy, along with its own release numbers (1.4 the latest one). As such, 
and considering it's such a small application with little development happening, it's a bit overkill to do a 
gnome-3-30 branch to deal with this and instead I'll simply keep the change in master and include it in the 
next stable release whenever it happens (in the next weeks, hopefully).

It's true that's a bit too quick for a non-code app to adopt this change, but I have no clue of when I'll 
have time to do it in the future, so I rather release it sooner than later :-).

> > I'm planning to make a release of frogr in the next days/weeks and it would be great if the i18n teams 
> > could get that fixed, since it's very visible being in the hamburger menu. I fixed en_GB, es_ES, gl_ES, 
> > pt_PT, pt_BR and fr_FR myself, but there are others I dare not touch, for obvious reasons :-)
>
> If you’re talking about a 3.30 release, see my remark above. If you’re
> talking about a 3.31 release, then not being translated is not a big
> deal and it is fine for translators to wait until closer to the 3.32
> freeze. Also, you shouldn’t ever “fix” translations.

As mentioned to Alexandre, being a native Galician & Spanish speaker who also speaks English and a bit of 
Portuguese (and even very little French), combined with the fact that it was such a simple string to fix, I 
thought it would qualify as a "trivial change" and went ahead precisely to avoid bothering those i18 teams.

But, as Alexandre wisely pointed out, that has other problems such as skipping the normal workflows and 
risking a worsened QA process, so I think it was wrong for me to do it and I openly apologize for that. 
Thanks Alexandre for pointing it out.

Thanks everyone!
Mario