Hey,
I just commited a reconfiguration of the repository layout. I introduced
basically three directories. With this I follow a rather standard directory
policy in revision control systems. I will detail what the directories are
for below.
trunk/
This directory is for the main line of development. I moved the former
contents into this directory.
branches/
Should we have the need for parallel lines of development just copy the
current (or an older) state of trunk here with the command:
svn cp trunk branches/newBranch
The so created branches can lateron easily be merged back into the main
development line when they have reached maturation.
tags/
This directory can be used to preserve old states of the code. For example
when we have releases we can just copy the state of trunk at release time
into there and can lateron easily identify and retrieve the state of the code
that was released.
In CVS there is the concept of tagging individual commits. But this here is an
easier way of doing it.
Using this new directory strucutre we could for example introduce now a
0.2-release-candidate branch to make it really stable and robust so that it
reaches release quality. The question would then be whether we wait until
Karsten's present work is finished or whether we want to release the prior
state as 0.2 and have his work lead to 0.3. What do you think?
PS: Do you think we should include the data/ directory into trunk/ or have it
seperately?
Kind regards, Jonas.
|
