On Thu, Jul 31, 2014 at 5:24 PM, Sébastien Wilmet <[email protected]> wrote: > Hi,
Hi, > At some rare occasions, especially after the string freeze, translation > commits are pushed when rolling a tarball for making a new release. > Since the commit for the release should be pushed only when 'make > distcheck' has succeeded, there can be a push conflict and the > maintainer have to repeat the process (sometimes several times). > > I think it would be nice to send mails on gnome-i18n and gnome-doc-list > to explain that commits should not be pushed during the release days. If > a translation or documentation commit is important, the maintainers can > anyway be contacted on IRC to know if the commit can be pushed. > > I think there is no equivalent of 'svn lock' for git, so sending a mail > is a solution. > > Bonus point is to add a warning on l10n.gnome.org, but it is more work. > > What do you think? +1. > Is it too rare to care about this problem? I don't think so but being a maintainer for years, you'll learn to do `git push origin master` first always. :) -- Regards, Zeeshan Ali (Khattak) ________________________________________ Befriend GNOME: http://www.gnome.org/friends/ _______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
