For those of you who have been keeping up with or checking out from the SVN (all 3 of you...), as of r51 there's been a small change which should be a welcoming move to anyone who's ever used SVN before. We've split Enigma up into trunk, tags, and branches.
This move came after we realized that serprex was apparently trying to create a branch but we didn't have the t/t/b structure in place.What this means:
> If you don't use the SVN, this means nothing to you.
> If you checked out from the SVN already and do a regular svn update or svn commit, you will need to do a one-time svn switch
> svn switch https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/trunk
> If you wish to check out a fresh copy of enigma from the SVN, you'll need to append /trunk to the URL.
> svn co https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/trunk
> If you wish to work on or check out the branch that serprex seems to want to work on, you can do an svn switch to the branch:
> svn switch https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/branch/enigma-devWhat are branches, tags, and trunk?
Developers sometimes like to copy the entire project to a few locations so they can keep backups or work on changes without screwing up other parts.
is a stable copy. This is usually used to tag releases and betas with specific revisions. There can be multiple tags, and they are usually pretty stable, and usually don't change.
is the main copy. This is where all the main development goes on. There is only one trunk, and it is moderately stable/unstable. Usually for stable versions, you will be recommended to a specific revision number.
is a specific development copy. When someone wants to try an experiment or implement a new big feature, they will oftentimes create a branch and work on it there, so that they don't disturb the main development (trunk) with their changes until they are done, and they merge it back with the trunk. There can be multiple branches going on at once, and they are usually quite unstable.More advanced things:
> Creating new branches, or merging the existing branch back with the original project, should be as simple as calls to svn copy and svn merge, respectively. The SVN Book should be a handy resource here, particularly the chapter on Branching and Merging:
These changes and their explanations courtesy of