[Geany-devel] Branching im geany-plugins SVN

[Frank Lanitz]

Hi guys, 

As you might have seen, last week I created a branch for redesigning of
GeanyVC's menu structure. For creating this, I branched the geanyvc
subfolder from trunk. This was ok IMHO for this topic but made me
thinking about how a branch could look like in future. I had a couple
of ideas and like to start some kind of poll about this topic ;) 

1.) Always branch complete trunk with all plugins so e.g. waf is still
working. This would make some things more easier e.g. handling with git
svn, but would force somebody who did a svn co on the branch to waste
space on the hard drive 

2.) Creating a folder structure similar to the tags section and then
putting the branch into the right folder:

|-- branches
|   |-- backupcopy
|   |-- filetree
|   |-- geany-mini-script
|   |-- geanydbg
|   |-- geanydebug
|   |-- geanydoc
|   |-- geanylatex
|   |-- geanyprj
|   |-- geanysendmail
|   |-- geanyvc
|   |-- instantsave
|   `-- spellcheck
|-- tags
|   |-- backupcopy
|   |-- filetree
|   |-- geany-mini-script
|   |-- geanydbg
|   |-- geanydebug
|   |-- geanydoc
|   |-- geanylatex
|   |-- geanyprj
|   |-- geanysendmail
|   |-- geanyvc
|   |-- instantsave
|   `-- spellcheck
`-- trunk

3.) Branching as needed analog to GeanyVC_menu_redesign, were only
code is included, that is really needed for the branch. 

I'd prefer suggestion 1, but I really like to know your opinion. ;)

Cheers, 
Frank
-- 
http://frank.uvena.de/en/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.geany.org/pipermail/devel/attachments/20090130/bd40c90a/attachment.pgp>