Re: Translation commits pushed when rolling a tarball
On Thu, Jul 31, 2014 at 5:24 PM, Sébastien Wilmet swil...@gnome.org 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 desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Translation commits pushed when rolling a tarball
On Thu, Jul 31, 2014 at 05:24:55PM +0200, Sébastien Wilmet wrote: I think there is no equivalent of 'svn lock' for git, so sending a mail is a solution. I think we could add something as equivalent to svn lock. It takes a bit of time to setup though, and damned lies (l10n.gnome.org) would have to be able to handle errors from git.gnome.org. If enough devs speak up I could maybe make something to lock a repository against pushes. Maybe with a timeout, maybe not. With SVN anyone could force a lock to be removed. Not sure of what is best. I assume a lock should at most be held for 2 hours. I'd appreciate a bit of insight from some tarball creators aka maintainers :-P -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Translation commits pushed when rolling a tarball
On 08/01/2014 05:22 PM, Olav Vitters wrote: I'd appreciate a bit of insight from some tarball creators aka maintainers :-P I personally don't mind at all if someone pushes translation fixes while I'm rolling a tarball. It's not really much of a problem for me to run 'make distcheck' once more to pick up additional translation goodness. -- Kalev ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Screenshot automation BoF at GUADEC
Am 14.07.14 17:43, schrieb Alexandre Franke: Hi, It's 2014 and translators and documentation writers still have to spend a lot of time to manually create screenshots. There must be a better way. Therefore I'm planning a half-day BoF on this topic at GUADEC. This is relevant to you if you're a translator or writer, but we also hope people with experience in automated UI testing will show up to give us a hand. Hi, I develop, document and translate in GIMP and like to know more about this topic. Can you already tell me about results of your BoF session at GUADEC, please? Thank you in advance Sven ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Translation commits pushed when rolling a tarball
On Fri, 2014-08-01 at 18:40 +0200, Kalev Lember wrote: It's not really much of a problem for me to run 'make distcheck' once more to pick up additional translation goodness. For stable releases taking the latest translations is important, but for unstable releases it's not a big deal if the translation is for the next beta. Making releases is not the funniest part of a maintainer work, even if push conflicts are rare (at least for me), the fact that I know it can happen doesn't put me in a comfortable position when rolling a tarball (it's more on the psychological side). Sébastien ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.14 Blocker Bugs
A first list of blockers and potential blockers for the upcoming release, based on data in GNOME Bugzilla. Note that there are lots of gnome-themes-standard/HighContrast tickets open. Please take a quick look at the list below, comment (on the ticket), and raise your voice if you see an important issue missing. Thanks! andre == GNOME-CONTROL-CENTER == background: thumbnails are tiny in 3.13.3 https://bugzilla.gnome.org/show_bug.cgi?id=732375 == GNOME-SHELL == desktop menu went missing https://bugzilla.gnome.org/show_bug.cgi?id=731932 Invalid backlight level at startup https://bugzilla.gnome.org/show_bug.cgi?id=727048 == GNOME-THEMES-STANDARD == HighContrast: calendar theming https://bugzilla.gnome.org/show_bug.cgi?id=732490 HighContrast: all white in gtk3-widget-factory https://bugzilla.gnome.org/show_bug.cgi?id=732482 HighContrast: flat button love https://bugzilla.gnome.org/show_bug.cgi?id=732492 HighContrast: invisible pane splitter https://bugzilla.gnome.org/show_bug.cgi?id=732485 HighContrast: expander hover state https://bugzilla.gnome.org/show_bug.cgi?id=732495 HighContrast: inconsistent toggle button unreadable https://bugzilla.gnome.org/show_bug.cgi?id=732487 HighContrast: neuter the statusbar frame https://bugzilla.gnome.org/show_bug.cgi?id=732489 HighContrast: no padding in actionbars https://bugzilla.gnome.org/show_bug.cgi?id=732491 HighContrast: vertical spin buttons look bad https://bugzilla.gnome.org/show_bug.cgi?id=732483 HighContrast: suggested/destructive-action https://bugzilla.gnome.org/show_bug.cgi?id=732493 HighContrast: broken hover for check/radio buttons https://bugzilla.gnome.org/show_bug.cgi?id=732486 HighContrast: popover background missing https://bugzilla.gnome.org/show_bug.cgi?id=732488 == GTK+ == popovers can't always track the widget https://bugzilla.gnome.org/show_bug.cgi?id=729140 gtk-demo: entry completion doesn't work https://bugzilla.gnome.org/show_bug.cgi?id=695504 treeview: column drop target visualization broken https://bugzilla.gnome.org/show_bug.cgi?id=732916 == MUTTER == [regression] Can't turn off wayland https://bugzilla.gnome.org/show_bug.cgi?id=729490 == POLARI == polari 3.13.2 has a lot of transparent text, making it almost impossible to use https://bugzilla.gnome.org/show_bug.cgi?id=734100 Should be fixed already. ===Further bugs that would be good to fix or get progress with:=== == GNOME-NIBBLES == Remove statusbar https://bugzilla.gnome.org/show_bug.cgi?id=666501 == GNOME-SHELL == Modal password boxes prevent users from looking up or generating passwords https://bugzilla.gnome.org/show_bug.cgi?id=688434 == GNOME-SUDOKU == no indication that i've run out of puzzles in print multiple sudokus https://bugzilla.gnome.org/show_bug.cgi?id=580055 gnome-sudoku generates invalid puzzles https://bugzilla.gnome.org/show_bug.cgi?id=619190 == GTK+ == Message dialogs - padding and text justification issues https://bugzilla.gnome.org/show_bug.cgi?id=732882 GtkPlacesSidebar - refine spacing https://bugzilla.gnome.org/show_bug.cgi?id=731443 == TOTEM == Add Favorites/bookmarks https://bugzilla.gnome.org/show_bug.cgi?id=357843 -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.14 Blocker Bugs
On Sat, 2014-08-02 at 00:22 +0200, Andre Klapper wrote: A first list of blockers and potential blockers for the upcoming release, based on data in GNOME Bugzilla. Note that there are lots of gnome-themes-standard/HighContrast tickets open. Please take a quick look at the list below, comment (on the ticket), and raise your voice if you see an important issue missing. I've removed the Nibbles and Sudoku bugs which I didn't intend to be on this list; sorry about that. I think https://bugzilla.gnome.org/show_bug.cgi?id=730478 is serious and should be added. signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Translation commits pushed when rolling a tarball
On Fri, 2014-08-01 at 11:31 +0200, Zeeshan Ali (Khattak) wrote: I don't think so but being a maintainer for years, you'll learn to do `git push origin master` first always. :) 'make distcheck' sometimes fails, for example a file which is not distributed in tarballs. Maybe GNOME Continuous could run 'make distcheck' on (almost) every commit? To detect such errors earlier than the release day. Sébastien ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
