Re: Re: [dev] Mercurial-Implementation: OOo domain developer public keys
Jens-Heiner Rechtien <[email protected]>
| Newsgroups | gmane.comp.openoffice.devel.tools |
|---|---|
| Message-ID | <[email protected]> |
Hi Jan, "release branch" is fine with me, but DEV300 is exactly not a "release branch". "Trunk" doesn't sound right as well. "development branch" might work. I tend to call a MWS nowadays a "major code line" but that's kinda ugly as well. For the term CWS it's even more difficult: a CWS is much more for us than just a "feature branch" and it might actually not contain a feature at all. I'm all for a more streamlined jargon, but it might be not that easy to find something which is precise and concise and universally understandably at the same time. Suggestions for a coherent nomenclature are welcome! Heiner Jan Holesovsky wrote: > Hi Heiner, > > On Friday 28 August 2009, Jens-Heiner Rechtien wrote: > >> Please contact me if you have problems, suggestions etc. > > Actually, I have a suggestion ;-) > > Do you think - with the switch to Mercurial - would it be possible to stop > using the 'CWS' and 'MWS' terminology, and instead switch to the commonly > used 'feature branch' and 'release branch' terms? > > Thank you, > Kendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >