Revisiting the translation freeze policies
Randy Barlow <[email protected]>
| Newsgroups | gmane.linux.redhat.fedora.devel,gmane.linux.redhat.internationalization |
|---|---|
| Message-ID | <[email protected]> |
Greetings! 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? * Can we automate some way of enforcing or at least detecting when something changes a string in the freeze? This ticket tracks the issue: https://pagure.io/fesco/issue/1777 [0] https://meetbot.fedoraproject.org/teams/fesco/fesco.2017-09-22-16.00.html _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJZySV0AAoJEHhEzLg73SRigz0P/3r0jxq9GOgs9eLSTdks3PLq ljPfVje/bUlL4/A0n9FKvFJKH9GRHqv6UQSjm2u/HetPthnMnC4bSHes943h6uxU WBGI65oSqnPH/4ydxnYXYFLRgZKdZJyOJ1+3/k1rweb4jbJ4RgclI8FNAXw+xeLo y4LQalR/USLA9iLv1fToO49qrqn42SPxOtqO2wznqgFTRaP89+J4p3SDa8lIPOQr MLnFP0mekXzVQe8oXcx4WCCUlFkeOZq3YuteANgB9O4EjvopjPeq0DiSm+7mNVZ0 8VoHwOKlQbCaP/ns8E7v5uY43q1LX8/c3mi+L1UUkLg6xAuP9FTRAupnPCezEwsg LORFi4o270UDa5UkbEtnbxlAZFR/kRJquNwSir0z0ytpC9kzkPLEIVjymeB7TU9W 7pRF3AK/QUrr35XZ2Mi9U83ze3uy4H9ZcOua00GjkOQ97C+3NFEt2+k5BYhZUmmG SJmyyfY9oi/jlTw+sfE2ADnn4voZroB05HiRp7fcgwsvufcMstljuZNMeN7KX1NL k7j8brng8jz/5D0CDKatpitbTj2yrOe7UEt9ZPcjqQKrxJp604Rq/oKlAh0xdR7K YUSEUsd/CDxq3m6c6vbdirSbmSyujNhojouQ+PoxkWbWwwIv7d7vohe3fqEeiQFL rbozqVQhD5H4QKlL+hox =mEKT -----END PGP SIGNATURE-----