On 09.08.2013 23:54, Johan Corveleyn wrote:
> On Fri, Aug 9, 2013 at 4:41 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>> On Thu, Aug 8, 2013 at 8:39 PM, Daniel Shahaf <danielsh_at_elego.de> wrote:
>>> Mattias Engdegård wrote on Thu, Aug 08, 2013 at 19:40:00 +0200:
>>>> 8 aug 2013 kl. 08.21 skrev Daniel Shahaf:
>>>>> Mattias Engdegård wrote on Wed, Aug 07, 2013 at 23:43:36 +0200:
>>>>>> Sorry about the late reply; I rarely have time to read the
>>>>>> list. It seems unlikely that many translators do - how are they
>>>>>> about the need to update their translations? It is common to have
>>>>>> this as
>>>>>> an explicit step in the release process; perhaps I have missed the
>>>>>> broadcasts so far.
>>>>> We don't have such a step. I don't know if such announcements have
>>>>> sent, but .de translator Jens Seidel also expressed interest in having
>>>>> such --- so perhaps we [c|sh]ould do that in the future.
>>>> Please consider that a strong suggestion then. After all, there can be
>>>> no surprise at the lack of translations if nobody thought of telling the
>>>> The usual way is to alert the translators when a release is about to be
>>>> made, but leaving them some time to actually do the work -- maybe a week
>>>> or two. It could be a good idea to notify them each time a new release
>>>> branch is forked off as well, since a lot of strings may have changed
>>>> from the previous release and that will give a little more time for
>>> Should we retroactively send a round of "Hey, 1.8.x has been released,
>>> please update translations on trunk and 1.8.x" ?
>>> Can you update docs/community/releasing.part.html or roadmap.html with
>>> a reminder to consider sending a Call For Translations to translators?
>> Just following this discussion from a distance, but: do we have a
>> "translation manager" ? Seems like this "alert the translators"
>> task (and keeping tabs on whoever are the current active translators
>> to keep in the loop) is a pretty good fit for such a person. If we
>> don't have an active translation manager at this time, perhaps someone
>> would like to volunteer?
>>  http://producingoss.com/en/share-management.html#translation-manager
> Or, as Daniel replied to me offlist, it would also be great if someone
> volunteered just for this specific task of soliciting translations
> from existing translators when 1.9.0-rc1 is announced (and perhaps
> retro-actively poll people for 1.8). This person doesn't necessarily
> need to take on more responsibilities.
Why do we need a volunteer? We can just teach release.py to generate the
e-mail (same as for announcements) and document this in the release process.
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
Received on 2013-08-10 00:02:19 CEST