Re: Question: more languages to support alternative month names?

[Rafal Luzynski <digitalfreak at lingonborough dot com>]

15.02.2018 22:30 Carlos O'Donell <carlos@redhat.com> wrote:
>
> On 02/12/2018 05:45 PM, Rafal Luzynski wrote:
> > Hi,
> >
> > Bug 10871 has been fixed and any language and any application can have
> > a choice between two grammatical cases of the month names. But having
> > a choice does not mean actually using it. I had only little more
> > than one week between accepting the change by the community and the final
> > release date so I was unable to contact every language community to
> > ask about their opinion. Only 7 languages have been fixed so far while
> > I have identified about 20 probably needing an update. 4 out of them
> > probably don't want two grammatical cases. There are ~9 more languages
> > who I'm contacting only now. It seems to me that at least few of them
> > will want this change. So my question is: if they agree how to provide
> > them the change:
> >
> > * push the change to master and tell them that they have to wait
> > for glibc 2.28?
> > * push the change both to 2.27 and 2.28?
> >
> > [...]
>
> You can do either option depending on how much free time you have.
>
> Fedora *routinely* imports upstream release branches.
>
> For example Fedora 28 will be based on glibc 2.27, and over the
> 6 months of support for Fedora 28 it will be updated routinely
> from upstream release/2.27/master to pull in the latest fixes.
>
> There are other distributions doing much the same, and I know Debian
> probably also rebases on releases branches.
>
> So you can do either.
>
> As the localedata subsystem maintainer you can commit the fixes to
> master and cherry-pick into 2.27 release branch immediately after.

So I have 4 patches ready to be committed for the following languages:

ca_ES: https://sourceware.org/ml/libc-alpha/2018-03/msg00166.html
lt_LT: https://sourceware.org/ml/libc-alpha/2018-03/msg00202.html
el_*:  https://sourceware.org/ml/libc-alpha/2018-03/msg00203.html
cs:CZ: https://sourceware.org/ml/libc-alpha/2018-03/msg00325.html

lt_LT fixes 2 strings (month names), it is a minor change.  el_CY
and el_GR add ab_alt_mon which turned out to be necessary but this
is not a major change taking into account that altmon is already
present in el_* locales.  cs_CZ introduces altmon; it has been
discussed for a long time but glib2 translator has already provided
the equivalent translation, it will be used as a fallback for older
systems so it does not make sense *not* to support the genitive
cases in cs_CZ in 2.27.  ca_ES introduces altmon, ab_alt_mon, and
few minor typo changes as requested by the translator.  The
translations for GNOME project have been already adapted to the
new format ("%d de %B" replaced with "%d %B").

IIUC it is OK to commit these changes to master.

Also I'd like to cherry-pick them all into 2.27 release branch.
Can you guys explain me the process of committing to the stable
branch? I should update ChangeLog, that is obvious.  What about
NEWS?  Should I retroactively add new languages and bugs to the
list of languages supporting the genitive case of month names
and to the list of bugs fixed in 2.27, just as if they were fixed
2 months ago?  Create a new section for 2.27.1?  Do not update
NEWS?  Do not cherry-pick anything to 2.27?

Regards,

Rafal