Re: Re: [dev] Mercurial-Implementation: OOo domain developer public keys

Hi *,

On Fri, Aug 28, 2009 at 5:46 PM, Jan Holesovsky<[email protected]> wrote:
>
>> Suggestions for a coherent nomenclature are welcome!
>
> Well, I was thinking the git way once again, sorry :-(
>
> But anyway, 'trunk' or 'main repository' (for DEV300), 'feature repository'
> (for OOO300, OOO310, ...),  and 'release repository' (for CWSes) sound best
> to me.

Oh, that is the exact opposite of my understanding.
OK with "main" for DEV300, but the OOO ones are the release ones,
that's where the releases are based on after all. And new features
won't be added on those. So calling OOO ones "feature branches" would
be confusing at best.
Similar for the cws - you won't buid a release based on a cws branch,
so thats a misnomer as well.

Honestly, I don't see a problem with just staying with cws branch. It
might be a term only used by OOo, but well, OOo's development model
just is different from just having a dev and release branch where
everybody commits directly...

ciao
Christian