Re: [Zopexmlmethods-devel] cvs administration

[Craeg K S. <cs...@ar...>]

I like the naming conventions, they look fine...

..but urge caution as far as creating CVS branches goes.

When you create a branch,
- it is harder for others to see what you are doing
- the eventual merge gets more difficult over time
- you lose the intangible benefits of collaboration

Having said that, there may well be reason to create a branch,
but why don't you try first giving your ideas an airing on the mailing list,
and see if we can't implement some or all of them on the mainline?

Personally, I am a big fan of merciless refactoring, as long as it is
backed by a strong suite of tests.  When you say "purely structural"
I assume you mean refactoring, yes?

--Craeg

Philipp von Weitershausen wrote:

>Hi all(?),
>
>I just got my CVS checkout. I have some plans and ideas, one of them are purely
>structural. I propose that I will make my own branch which I would call
>'philikon-branch'. How shall we name branches and tags? Upper case, lower case,
>camel case?
>
>I propose:
>
>- tags uppercase and underscores, e.g. RELEASE_1_0
>
>- branches lowercase and hyphens, e.g. philikon-branch
>
>- merge tags on the branch mixed, e.g. philikon-RENAMING_MERGE
>
>Comments?
>
>Philipp
>  
>