Re: Repository change to SVN, Jan 28th

[Sheldon Gill]

Fred Kiefer wrote:
> I also think that with the new possibilities of SVN there come a few
> more rules that we need to set up and follow. We expect that SVN will
> make it easier to have multiple branches with actual development going
> on. Now what will be the rules for merging this branches back into the
> main trunk? At work we are using ClearCase and have rather complicated
> procedures that have to be followed to make this step save. Something
> simpler might be enough for GNUstep. At least all changes from the trunk
> need to be merged down first, conficts resolved and the code tested.
> Then a review could happen, before the changes get actually merged.

Actually, I think Fred has raised a good point here. We do, I think, need some 
clarification about branches and merging back to trunk. A few additional rules 
and guidelines may be useful. I've some questions:

  - are we going to stick with the SVN recommended 'trunk', 'branch' and 'tag'
  - how are branches to be named? What about sub-branches?
  - how are developers going to communicate about branches and what's going on 
in them?
  - what goes into tag? When?
  - Are we going to import more vendor trees? (like ffcall, portaudio etc)

Things to think about.

Regards,
Sheldon