This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.25 development --- 46 days to freeze.
- From: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- To: Jochen Hein <jochen at jochen dot org>, Carlos O'Donell <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Sun, 20 Nov 2016 10:09:54 +0530
- Subject: Re: glibc 2.25 development --- 46 days to freeze.
- Authentication-results: sourceware.org; auth=none
- References: <21b86aae-e2b2-2bc6-e689-0597e76bbfad@redhat.com> <8360nom0gl.fsf@echidna.jochen.org>
On Wednesday 16 November 2016 11:26 AM, Jochen Hein wrote:
> Can we get a snapshot of the current pot-file out to the translators? We
> missed the last two releases, so I guess we need some time to catch up.
> We can (and should) refresh the pot file after the freeze to translate
> the last (hopefully few) messages before the release.
I think that is a good idea. In fact, would it be more productive to
tweak the current workflow a bit so that translators can pull directly
from git instead of using tarballs? I am referring to the libc.pot
workflow documented in our Release wiki[1] that requires the release
manager to upload a tarball and then email coordinator AT
translationproject DOT org. Instead, the glibc release manager could
just send out the email when they update libc.pot and translators can
pull from git. I reckon this could even be automated in a git
post-commit hook.
Thoughts?
Siddhesh
[1] https://sourceware.org/glibc/wiki/Release