[Localization] [sugar] Branch rename, update-1 -> ship-2

[Jim Gettys]

No, we have update.1...  We had to quickly do Ship.2 to fix some
pressing wireless and upgrade problems....

See: https://dev.laptop.org/roadmap for details.
                       - Jim


On Tue, 2007-12-11 at 00:47 +0530, Sayamindu Dasgupta wrote:
> Hi,
> Apologies for the delayed reply.
> 
> On Dec 7, 2007 3:38 PM, Marco Pesenti Gritti <mpgritti at gmail.com> wrote:
> > On Dec 7, 2007 10:25 AM, Sayamindu Dasgupta <sayamindu at gmail.com> wrote:
> > > Hi Marco,
> > > How do we "switch" to the ship-2 branch in such a case ? Do the normal
> > > rules apply, or is there any simpler procedure (since this is a simple
> > > rename) ?
> >
> > I'm not sure how pootle is handling branches, but yeah this is
> > basically just another branch.
> 
> So the update-1 branch no longer exists, and we have ship-2 branch in
> place - right ?
> 
> > Btw it would be good to chat about the update-1 branches which we
> > started to create, if you have any time today...
> >
> 
> We are using a system where we have a directory (update1_core) where
> all the modules which have an update-1 branch are kept (with the
> active branch being update-1). Pootle sees a file called
> translations/update-1/xx/module.po which is a symlink to
> checkouts/update-1/modules/po/xx.po. Thus Pootle thinks that Update 1
> (Core) is a single project with multiple PO files to translate.
> We have a few scripts to handle this symlinking and to ensure sanity
> (no invalid links, no non-symlink files in translations/).
> This makes things a bit complicated at our end, but makes the job of
> the translation coordinator for a particular team easy, and it is also
> easy to gather overall statistics.
> 
> I'll be on IRC for the entire day tomorrow - feel free to ping me
> anytime (my nick is unmadindu)
> 
> 
> Warm regards,
> Sayamindu
> 
-- 
Jim Gettys
One Laptop Per Child