Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-12 Thread Luigi Toscano
On Friday, 9 September 2016 14:12:51 CEST Matt Riedemann wrote: > On 9/9/2016 1:58 PM, Ben Swartzlander wrote: > > On 09/08/2016 08:37 PM, Matt Riedemann wrote: > >> On 9/8/2016 7:05 PM, Ravi, Goutham wrote: > >>> Hi, > >>> > >>> > >>> > >>> I was looking for some clarity around backports of bug

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-09 Thread Nikhil Komawar
I have had some questions offline so, I think documenting the theory, interpretations and POC will be helpful in our release schedule pages to get this practice consistent across projects. If not required (or if the process is subjective) we do not necessarily have to enforce strict process, but we

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-09 Thread Matt Riedemann
On 9/9/2016 1:58 PM, Ben Swartzlander wrote: On 09/08/2016 08:37 PM, Matt Riedemann wrote: On 9/8/2016 7:05 PM, Ravi, Goutham wrote: Hi, I was looking for some clarity around backports of bug fixes that qualify the stable branch policy [1].

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-09 Thread Ben Swartzlander
On 09/08/2016 08:37 PM, Matt Riedemann wrote: On 9/8/2016 7:05 PM, Ravi, Goutham wrote: Hi, I was looking for some clarity around backports of bug fixes that qualify the stable branch policy [1]. What is th

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-09 Thread Tony Breeds
On Fri, Sep 09, 2016 at 11:17:17AM +0200, Andreas Jaeger wrote: > On 09/09/2016 04:34 AM, Tony Breeds wrote: > > [...] > > I did a spot check and it seems like liberty is closed for translations. > > Yes, liberty is closed for translations now, Thanks Andreas. Yours Tony. signature.asc Descrip

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-09 Thread Andreas Jaeger
On 09/09/2016 04:34 AM, Tony Breeds wrote: > [...] > I did a spot check and it seems like liberty is closed for translations. Yes, liberty is closed for translations now, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nü

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-08 Thread Tony Breeds
On Thu, Sep 08, 2016 at 07:37:40PM -0500, Matt Riedemann wrote: > The former IMO, a high severity bug fix trumps a translation. Note that some > projects are translated on the stable branches too, I know this is the case > for Nova. > > If it's a user-facing change, like an error message in the A

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-08 Thread Matt Riedemann
On 9/8/2016 7:05 PM, Ravi, Goutham wrote: Hi, I was looking for some clarity around backports of bug fixes that qualify the stable branch policy [1]. What is the policy if the fix introduces a new translatabl

[openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-08 Thread Ravi, Goutham
Hi, I was looking for some clarity around backports of bug fixes that qualify the stable branch policy [1]. What is the policy if the fix introduces a new translatable string or modifies an existing one? The g