Re: Translations gone out for 2.16.

[Carlos O'Donell <carlos_odonell at mentor dot com>]

On 6/26/2012 12:53 PM, Joseph S. Myers wrote:
> On Tue, 26 Jun 2012, Carlos O'Donell wrote:
> 
>> (3) Where on sourceware.org were the snapshots placed?
> 
> Directory /sourceware/ftp/anonftp/pub/glibc/snapshots (you need an account 
> with shell access to place things there).  It looks rather like they were 
> automatically generated from CVS and stopped with the move to git.  This 
> maps to ftp://sourceware.org/pub/glibc/snapshots/.

Thanks. I'll keep this location in mind if we need to store other things there.

For now I'm going to use alpha.gnu.org for snapshots.

>> (4) What version number to use?
>>
>> I will document that we should use `X.Y.DATE' for the snapshots
>> that we send to alpha.gnu.org for TP to use. Following the
>> alternate recommendation from the maintainers guide.
>>
>> The TP instructions say nothing about what version number to use,
>> they only say that translations will happen *once* for any given
>> version number.
> 
> There used to be TP documentation about how versions were ordered.  The 
> instructions I wrote at <http://gcc.gnu.org/translation.html> about using 
> "gcc-<version>-b<date>.pot" were based on that documentation - the "b" was 
> supposed to mark beta releases as older than the actual release.
> 
> That no longer seems to be documented.  However, I think the clearest 
> thing to do is to use a .90 version - after all, version.h does say 
> "2.15.90" - along with a date (for example, 2.15.90.20120625).  That makes 
> the ordering with respect to both 2.15 and 2.16 completely clear to 
> everyone.

That sounds good to me.

(1) For trunk snapshots I'll use X.Y.90+N.YYYYMMDD, with N starting at 0.
(2) For stable snapshots I'll use X.Y.N.YYYYMMDD, with N starting at 1 since 0 was already released.

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026