Greg Stein wrote:
> On Tue, Jan 27, 2009 at 11:52, Julian Foad <julianfoad_at_btopenworld.com> wrote:
>> I think an email list is the best way to manage notifying a group of
>> translators when a release is being prepared, and maybe the <announce>
>> list is the best one. If so, perhaps we should agree to issue a "call
>> for translation" announcement when each release is being prepared, and
>> translators should subscribe to <announce>.
>> Can the release manager or other translators comment on that suggestion?
> hwright and I discussed this yesterday, and we dislike the idea.
> Consider: an email to reach a dozen or two translators, but sent to an
> email list intended to reach *thousands* of *users* ? I don't think
> that makes sense.
>> Can I suggest you subscribe to <announce> anyway, as at least you will
>> see the 1.6.0 release candidates being announced. Is that a good time to
>> do the translations?
> Well, a release candidate means "hey. we're done. no more changes,
> except to fix a *showstopper*". While translation updates are low
> risk, that is not a showstopper and a reason to create a new
We always roll at least 2 release candidates, one at the beginning of the soak,
and another about a week before the soak ends. Translation updates can continue
to flow into the release branch during the soak, so they'd be picked up in the
final rc, and hence the final tarball. If translators see the announcement for
rc1, then they'll know they have about 3 weeks to get their translations completed.
Received on 2009-01-27 15:30:23 CET