Hi Randy,
Sorry, I was bit of behind and gave improper comment previously. Now I think I caught up where we are. Let me do it again. Please see inline.

On Tue, Sep 26, 2017 at 5:18 AM, Randy Barlow <bowlofeggs@fedoraproject.org> wrote:

During Friday's FESCo meeting[0] we were asked to approve a change to
the release schedule to accommodate translation string freeze deadlines
that somehow got left out of the new "no-alphas" schedule.

Several participants pointed out that Fedora has not enforced the
"string freeze" in many years, despite it being on the schedule until
now. Thus, we would like to revisit the string freeze policy to
determine if it is still valuable, and if so, how can/should it be enforced?

We'd like to explore a couple of questions:

* What exact things are frozen? Things like comps make sense to follow
  Fedora freezes, but do things like anaconda? or system-config-printer?

I've read through those, and it seems to me still valid and important for Translation team.

For anaconda or s-c-printer, 'string freeze policy' should work. Most likely we've been giving +2. If any particular concern on the developers side, please share.


* Can we automate some way of enforcing or at least detecting when
  something changes a string in the freeze?

At last G11N FAD, i18n team raised their hand to explore some possibility of developing a tool for detection (String Breakage monitoring by Jens and Akira). Could you kindly check with i18n team as well?  Or Pravin can connect?

G11N FAD Tokyo Summary: https://docs.google.com/document/d/17LU-PmtuirbGd7wfxUuKTz7X6fsv82PVPgZaDELi4js/edit#heading=h.3gzh0ubdx8oy



This ticket tracks the issue:


trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-leave@lists.fedoraproject.org