[wp-polyglots] trunk or branches ?

[Kimmo Suominen]

Hi Xavier,

A branch, a tag and a copy are really just the same thing in svn.  While
the 1.5 branch may not see a lot of updates in the future, I thought it
is possible, and calling it a branch felt the most natural choice to me.
So the build.sh script is looking under branches rather than tags.

You do want to make a snapshot of everything, not just the messages
directory, so that you can get a consistent build of the translated
files.

I used these commands

    # use the language you work on instead of fi_FI
    cd /some/where/fi_FI
    svn copy trunk branches/1.5

Regards,
+ Kim
-- 
<A HREF="http://kimmo.suominen.com/">Kimmo Suominen</A>

On Thu, Mar 31, 2005 at 10:10:01AM +0200, Xavier Borderie wrote:
> Good day, gentle people.
> 
> I'd like to (at last) start working on the 1.5.1 POT, but still want
> to keep the original 1.5 PO/MO safe and sound. While it seems obvious
> that the work-in-progress for 1.5.1 should be located in
> /trunk/messages/, I'm just wonderering, and therefore asking for
> opinions, on where to store, indefinitely, the 1.5 files. Namely, I'm
> hesitating between these two locations in the repository :
> * /trunk/messages/1.5/
> * /branches/messages/1.5/
> 
> I find /trunk/ the more obvious choice, as it is not really a
> branching of the original PO, just a safekeeper in case of need, but
> hey, some other people, more used to SVN philosophy than I, may have a
> different opinion. So I'm asking : what's your safe bet ? How do you
> manage the different versions.
> 
> (I'm not planning on hosting the files on my own site, as we never
> know if I'm not gonna sell my domain to get super-mega-rich some day,
> and would rather use the repository as a central source for it all.)
> 
> Thanks.
> 
> x.