glade3 3.8.1
News - Correctly detect the required devhelp version (Javier Jardón) - Sort objects in output by property reference, ensures a GtkTreeModelFilter gets serialized after its 'child-model' (fixes bug 657164) - Fixed crashers when performing "Remove Parent" (bug 657338) - Ensure 'use-action-appearance' is serialized before 'related-action' (bug 658497) - Properly escape special characters while serializing property values (bug 654609 - Fabien Parent) - Fix GladeProject to notify "row-has-child-toggled", (fixes bug 651673). ChangeLog = http://download.gnome.org/sources/glade3/3.8/glade3-3.8.1.changes (1.68K) Download http://download.gnome.org/sources/glade3/3.8/glade3-3.8.1.tar.xz (2.21M) sha256sum: 4ca469d51ce1ce9ac84fae7b0cab0707700330454058b180f796f92881243cd1 http://download.gnome.org/sources/glade3/3.8/glade3-3.8.1.tar.bz2 (2.57M) sha256sum: 8844b66c3236afbc3cf768c1856d85f1da00a4c0dd6009bca58fa832e894c2cc ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Proposed Freeze Change
Hi! > > Consequently the same question goes for "String Change Announcement > > Period" - CC'ing gnome-i18n as I'm wondering if translators still > > consider the "String Change Announcement Period" useful. > > I'm all in favour of dropping it, for the following reasons: > 1. I doubt it is really useful for translators > 2. I think only a minority really announce new strings > 3. It would be easy to do something automatic from l10n.gnome.org if > needed Agreed, can we just merge the "String freeze" into the "The Freeze", too? Because if you cannot change UI/features it is unlikely that strings will change and if they do, as Shaun pointed out already, you just sent a mail. I18n didn't block many strings the the last cycles and it oftens gives us the oppertunity to fix the string (english, type, whatever) before it is commited. Regards, Johannes ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Proposed Freeze Change
2011-10-10 19:29 keltezéssel, Claude Paroz írta: Le lundi 10 octobre 2011 à 18:17 +0200, Andre Klapper a écrit : (...) Consequently the same question goes for "String Change Announcement Period" - CC'ing gnome-i18n as I'm wondering if translators still consider the "String Change Announcement Period" useful. I'm all in favour of dropping it, for the following reasons: 1. I doubt it is really useful for translators 2. I think only a minority really announce new strings 3. It would be easy to do something automatic from l10n.gnome.org if needed Claude +1 If I'd like to know if there is something new to translate, I go straight to damned-lies. Nothing else is needed. Regards Gabor Kelemen ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Proposed Freeze Change
Le lundi 10 octobre 2011 à 18:17 +0200, Andre Klapper a écrit : (...) > > Consequently the same question goes for "String Change Announcement > Period" - CC'ing gnome-i18n as I'm wondering if translators still > consider the "String Change Announcement Period" useful. I'm all in favour of dropping it, for the following reasons: 1. I doubt it is really useful for translators 2. I think only a minority really announce new strings 3. It would be easy to do something automatic from l10n.gnome.org if needed Claude -- www.2xlibre.net ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Proposed Freeze Change
[CC'ing release-team and gnome-i18n@.] On Wed, 2011-09-28 at 13:21 -0400, Shaun McCance wrote: > In the past, we've had three points in the schedule to help: > the UI change announcement period, the feature freeze, and the > UI freeze. Feature freeze is gone from the 3.3 schedule, which > confused me a bit, but I want to propose something different > anyway. > > The main problem is developer awareness. Developers don't know > exactly what constitutes a change that the documentation team > cares about. And it's sometimes hard to keep of which freezes > and announcement periods are in effect. Two-fold proposal: > > 1) Drop the UI change announcement period. It was a nice idea > at the time, but it just doesn't help me much. It's not worth > the developer mental overhead. > > 2) Merge the old feature freeze and the UI freeze into one big > freeze and call it something that suggests you're not supposed > to make changes. I've been calling it THE freeze. I'm not good > at naming things. Beta freeze? Software freeze? > > I had wanted to do the freeze with the 3.3.5 release, which is > where we would do feature freeze. But I fear it doesn't make > sense to do it before the Brno hackfest. > > When we're in the freeze, you don't make user-visible changes > anymore. No new supported formats or protocols or backends. > No new UI. No changes to how a user interacts with the UI. > You can fix crashes and address performance problems. > > In case you're worried this will stifle development, remember > that you have 21 weeks to go wild. That's 80% of the entire > cycle. And all you have to do to make a change is send an > email (or if we go with Bastien's proposal, file a bug). In > eight years, I only remember blocking one change proposal. For the time being I have added back a "Feature Implementation Freeze" to https://live.gnome.org/ThreePointThree for 3.3.5 (Feb 06th). I'd like to see a few more people (or at least more r-t folks) agreeing to 1) merge Feature Freeze and UI Freeze (which is at 3.3.90 currently) to "UI and Feature Freeze" and propose a date, and 2) whether to drop "UI change announcement period" completely. Consequently the same question goes for "String Change Announcement Period" - CC'ing gnome-i18n as I'm wondering if translators still consider the "String Change Announcement Period" useful. andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper | http://www.openismus.com ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[epiphany] Created branch gnome-3-2
The branch 'gnome-3-2' was created pointing to: 40a217d... Fixed Bug 660749. Call gtk_label_set_use_markup for the chi ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
