[Pkg-isocodes-devel] Submit pot file to TP before release?

[Tobias Toedter]

On Tuesday 17 October 2006 19:32, Alastair McKinstry wrote:
> Christian Perrier wrote:
> > I'm not deeply familiar with TP process, though. Tobias?

Hi,

the TP needs a download location for the tarball, it's not possible for us 
to upload the .pot files directly to them. The guys at the TP are fetching 
our tarball and put the .pot files online, after some sanity checks. That's 
the reason why the TP is lagging some days (sometimes up to two weeks) 
behind, they seem to have too much work to do.

> I think its worth doing this before any release that changes the list of
> entries;
> normally I've labelled these as the 'upstream' release.  We would do
> regular debian releases that just include additional translations; no
> need to ping the
> translators if the files to be translated have not changed.
>
> e.g. the next planned release (21st) is a 'debian' release; no need to
> upload to
> TP in advance of it.

Agreed. In addition, I'm not sure if the separation into "upstream" releases 
and "debian" releases is worth the effort. It only happens rarely that the 
msgids need updates, and we're constantly updating the translations. So any 
translator should see their work included within a few weeks (at most).

If we keep up our current release schedule (roughly every four weeks), we 
would not have a real benefit from the "release candidate" tarballs for the 
TP. Remember that they lag one or even two weeks behind.

Regards,
Tobias

-- 
Tobias Toedter   | "To be is to do"  -- Plato
Hamburg, Germany | "To do is to be"  -- Aristotle
                 | "Do be do be do"  -- Sinatra
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-isocodes-devel/attachments/20061018/4d4c0b5a/attachment.pgp