Hi Greg, On Friday, 2011-07-08 15:22:36 -0400, Greg Stein wrote:
> I'm going to suggest we do this: > > 3. as sibling to trunk and our other high-level directories: > > ooo/trunk/... > ooo/l10n/... +1 > That has the advantage of avoiding the l10n data when working on > trunk. When we copy trunk to a new branch, we can copy l10n into that > copied trunk, or as a sibling branch. I think that will depend on how > we'd like to manufacture a release, and I don't have the data for > that. I suggest to use a sibling also for new branches, that way working on a branch is similar to working on trunk. > [...] > Another option would be to use option (1), and if people don't want > the data, then they can use "shallow" working copies[1]. This requires > a bit more activity from the developer, and I think it would be > simpler to follow the *typical* case of not wanting the l10n data by > omitting it from trunk. Usually code developers don't need the l10n repo unless they want to build with an additional language. Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
pgpAufEpzOdTB.pgp
Description: PGP signature
