Re: String freeze break/creating a 3.6 branch?

["Zeeshan Ali (Khattak)" <zeeshanak gnome org>]

On Fri, Oct 19, 2012 at 12:33 PM, Christophe Fergeau
<cfergeau redhat com> wrote:
> Hey all,
>
> I've been too hasty in pushing a patch for
> https://bugzilla.gnome.org/show_bug.cgi?id=676340 (commit c2e55a9b6). This
> adds a few new strings, and thus breaks the 3.6 string freeze.
> I've mailed gnome-i18n to see how they feel about it (I was hoping that
> they'd say we can keep the strings as they are hidden in --checks ;), but
> so far their suggestion is to just branch for 3.6 before this commit (
> https://mail.gnome.org/archives/gnome-i18n/2012-October/msg00150.html ).
>
> An alternative would be to just revert this patch, but I think their
> suggestion makes sense.

Yeah, its fine by me.

> Apart from this commit, we could make sure we only
> commit to the 3.6 branch,

I don't see the point of that. I think all changes should first go to
unstable branch and if they are worthy of going to stable, we push
them there as well. In general, yes we should keep the 3.6 bugfixing
going for a bit but not too long or otherwise we wont get enough time
to finish new features or fix bugs that require breakage (like your
string breakage).

-- 
Regards,

Zeeshan Ali (Khattak)
FSF member#5124