Re: Translation commits pushed when rolling a tarball
- From: Sébastien Wilmet <swilmet gnome org>
- To: Ekaterina Gerasimova <kittykat3756 gmail com>
- Cc: desktop-devel-list <desktop-devel-list gnome org>
- Subject: Re: Translation commits pushed when rolling a tarball
- Date: Sat, 02 Aug 2014 14:24:48 +0200
On Sat, 2014-08-02 at 09:37 +0200, Ekaterina Gerasimova wrote:
Have you considered dropping an email to
gnome-doc-list gnome org and gnome-i18n gnome org lists before running
the distcheck? I found communicating with translators to be very
effective and the docs team would prefer communication over a ban.
With an equivalent of 'svn lock', there can be a friendly message
explaining that a developer is creating a release, and that the commit
can be pushed later (e.g. the following day). It is anyway temporary. I
wouldn't use the word "ban", I prefer the word "temporary lock", it is
less negative. Docs and translations commits are more than welcome, you
do a great job! It is just that the push conflicts can be a little
annoying.
But if each maintainer sends a mail to announce the distcheck to the
translation and doc teams, you'll receive hundreds mails, it doesn't
scale. Another mail should also be sent when the distcheck is finished.
Sending such mails is not convenient for the maintainer, and it assumes
that those mails are read as soon as they are sent.
Sébastien
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]