Hello,

As we previously discussed on IRC, I am taking over management of the 1.12 
stable branch for the remainder of its lifetime. Right now the dev team wants 
a 1.12.6 release out to ship some important fixes that have landed in the 1.12 
branch since the previous stable release, so a 1.12.6 release is what we'll 
have.

I will be tagging 1.12.6 next week's Wednesday, May 18th, after 00:00 UTC. I 
talked to the active devs and they decided that they wouldn't need to alter 
more strings for this release, so the customary pre-release string freeze on 
the 1.12 branch begins _now_.

So what does this mean for you? Let's see:

------------------------------------
For code contributors and developers
------------------------------------

The 1.12 branch is now under string freeze until 1.12.6 is tagged and 
announced. Most of you know the drill, but since there are a couple of new 
active contributors since the last time, I thought I would explain this again:

 * Commits altering translatable string contents are not allowed in the 1.12 
   branch until the string freeze is lifted.

 * Erasing strings, moving strings within the same textdomain, or adding new
   references to pre-existing strings within the same textdomain, are all 
   allowed actions for the duration of the string freeze.

 * master and feature branches are obviously not covered by this string 
   freeze.

---------------
For translators
---------------

There is one string change and one new string for you to work on. Make sure to 
send your updated .po files to Ivanovic *before* May 17th 00:00 UTC. Yes, you 
read that right, that's one day before the release ETA, so that we don't run 
into a situation where last-minute updates don't make it into the release 
because of time zone differences like last time.

-- 
Regards
  Ignacio R. Morelle <shadowm>

_______________________________________________
Wesnoth-i18n mailing list
Wesnoth-i18n@gna.org
https://mail.gna.org/listinfo/wesnoth-i18n

Reply via email to