logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Re: SF.net SVN: squirrelmail: [12649] branches: msg#00029

Subject: Re: SF.net SVN: squirrelmail: [12649] branches
> Kindly help me clarify how locales branches are treated in the SVN
> repository under the 1.4.x.
>
>> Revision: 12649
>> http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=12649&view=rev
>>  Author:   jervfors
>> Date:     2007-08-31 00:51:43 -0700 (Fri, 31 Aug 2007)
>>
>> Log Message:
>> -----------
>> Creating branches for SquirrelMail 1.4.10 and 1.4.11 translations.
>>
>> Added Paths:
>> -----------
>> branches/SM-1_4_10/ branches/SM-1_4_10/locales/ branches/SM-1_4_11/
>> branches/SM-1_4_11/locales/
>>
>> Copied: branches/SM-1_4_10/locales (from rev 12648, trunk/locales)
>>
>>
>> Copied: branches/SM-1_4_11/locales (from rev 12648, trunk/locales)
>
> a) Here the SM-1_4_10/locales and SM-1_4_11/locales branches were created
>  by copying those from trunk/locales, which is are the locales files for
> "current devel" (1.5.x), correct?

No. SquirrelMail HEAD (trunk/locales) contains both SquirrelMail DEVEL
(1.5.2 SVN) and SquirrelMail STABLE (1.4.11 SVN). Then, in commits 12651
and 12652 I updated "squirrelmail.pot" to contain only 1.4.10 and 1.4.11
strings respectively.

> b) If that [a] is the case (true), the assumption here must be that the
> same set of locales can be used for both 1.4.x and 1.5.x releases. Is
> this assumption in fact correct?

Everything but the "squirrelmail.pot" file.

> I see reason for these new branches existing (for reasons of clarity, for
> one), but it could be said that these branches are extraneous if in fact
> the locales for 1.4.x and 1.5.x are interchangeable? On the other hand,
> if they are not in fact interchangeable, then will copies of the
> translations for the 1.5.x codebase would not work, which would suggest
> that the assumption made in [b] is not correct.

They are very close to interchangeable.

> As you can see I observe what appears to be, from my standpoint, an
> inconsistency in how the locales are currently being handles within SVN.

I'm not very found of the way the locales are handled in the repository,
but it's the legacy and I haven't done anything to change it yet. Any
change requires the scripts that update the site with the data to be
rewritten, and I haven't had the time to do so, so we're sticking to the
legacy way for now.

> Finally, from where in the SVN repository were translations (locales) for
> 1.4.10a taken, before the above branch for that specific release was
> made?

We (I) haven't released any language packs for 1.4.10a, so they weren't
taken anywhere before I created that branch. I'm sorry about this.

> And last but not least, why was a branch created for 1.4.10 after the
> release ?

The branch should be created when the string freeze period, prior to the
release of a new SquirrelMail version, starts. I intended to release
language packs for 1.4.10 and 1.4.10a shortly after they were released,
but didn't (for private reasons not related to the SquirrelMail project).
As I wrote above, I'm sorry about this.

Feel free to get back to the list if you have any more questions about or
suggestions regarding how we handle locales in the repository.

Sincerely,
Fredrik


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/


<Prev in Thread] Current Thread [Next in Thread>