Re: Bison 2.4 release

[Tim Van Holder]

On 2008-11-05 15:52, Joel E. Denny wrote:
> On Wed, 5 Nov 2008, Tim Van Holder wrote:
> 
>> Would it be possible to adjust the Bison release procedures so that .po
>> files can be actually be made up to date for a release?
>> Sending in .pot files to the translation project AFTER the release
>> rather makes it impossible to get up-to-date translations into the
>> release tarball...
> 
> Hi Tim.  Thanks for the report, and sorry for the confusion this caused.
> 
> We had planned a 2.4.1 to catch new translations.  That is, 2.4 
> translations should work for 2.4.1.  There's already at least one minor 
> tweak to functionality that 2.4.1 will have as well, so we have another 
> reason to do this anyway.

> Now I'm still pretty ignorant about how the translation project works.  
> If we simply post the 2.4.1 tarball at some point without sending in .pot 
> files, will that be ok as long as there are no differences in translatable 
> strings?

Send in pot files too - they're merged automatically with all the .po
files in the TP.
In fact, this has been the case for the bison-runtime domain, as it
rarely sees changes. I get notified that there's a new version but it
just stays fully translated so there's no work for me.

Since bison tends to get alpha releases, I guess the easiest way to
ensure an up-to-date translation would be to ensure that a release must
always be based on a previous alpha release (with the only changes being
the version number). That way, there cannot be any change in the pot
file either.
As long as there is sufficient time between the last alpha and the
release (I'd say a week would be enough, but I don't know how quickly
the average translator updates a po file after being notified), this
would mean that the translations will have been mostly updated for the
alpha and will then be readily usable for the release too.