From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Jochen Hein <jochen@jochen.org>, Carlos O'Donell <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc 2.25 development --- 46 days to freeze.
Date: Sun, 20 Nov 2016 04:40:00 -0000 [thread overview]
Message-ID: <5f434f21-d9ae-b907-4647-26ae6e517eba@gotplt.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2016-11-20 4:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 20:55 Carlos O'Donell
2016-11-16 5:57 ` Jochen Hein
2016-11-20 4:40 ` Siddhesh Poyarekar [this message]
2016-11-20 6:11 ` Jochen Hein
2016-11-20 11:34 ` Benno Schulenberg
2016-11-20 13:08 ` Siddhesh Poyarekar
2016-12-01 13:32 ` Siddhesh Poyarekar
2016-12-01 16:03 ` Joseph Myers
2016-12-02 15:53 ` Carlos O'Donell
2016-12-02 15:57 ` Joseph Myers
2016-12-02 16:15 ` Carlos O'Donell
2016-12-02 15:54 ` Carlos O'Donell
2016-12-02 18:16 ` Siddhesh Poyarekar
2016-12-19 23:06 ` Carlos O'Donell
2016-12-20 16:54 ` Siddhesh Poyarekar
2016-12-02 18:18 ` Siddhesh Poyarekar
2016-12-19 14:24 ` Carlos O'Donell
2016-12-16 22:56 ` Mike Frysinger
2016-12-17 5:24 ` Siddhesh Poyarekar
2016-11-21 0:17 ` Nix
2016-11-22 18:58 ` Florian Weimer
2016-12-17 15:13 ` Zack Weinberg
2016-12-19 13:58 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f434f21-d9ae-b907-4647-26ae6e517eba@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=jochen@jochen.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).