Basic version of SVN

Question

Sorry, I'm new to SVN, and I looked around a bit. As you mark the major version in SVN, it’s kind of setting up a restore point. Right now I’m just setting up my server and adding all my files - I periodically rewrote different changes. When I have something in a stable state, is there a way to mark this so that I can return to it if necessary?

Answer 1

It looks like you are looking for tags.

Tags in Subversion Book

“A tag is just a snapshot of a project in time.”

Answer 2

A typical way is to create a tag directory in the root directory of your repository and copy the entire trunk to this directory. (Copying is cheap in Subversion because it simply adds links to specific versions of existing files.)

So you can say:

svn cp http://svn.example.com/trunk/ http://svn.example.com/tags/major-revision-01/ 

For more details, see the Subversion book , in particular tags .

Answer 3

Everything that we do, we create a branch. We have standard root directories: chest, tags, releases, branches.

The main thing to remember is that all branches are just like creating a copy, and all branches from the chest are like creating a copy (except that it is a shallow copy, only copying deltas).

For us, all development is carried out in the trunk. If someone does a big alteration, then, as a rule, puts him in the branches. The main issues are placed in the releases, and all other labels and elements that we want to mark are placed in the tag folder.

For our releases, we have the following directory structure:

 repository +--trunk +--releases +--v1.0 +--v1.1 +--v1.4 +--v2.0 +--branches +--tags 

Answer 4

Check tags

Answer 5

If you use the standard svn structure, you must have branches, tags, and a folder for external lines.

What you want to do is make a copy of the current trunk to the folder in the tags.

Command line example:

svn copy mysvnurl / myproject / trunk mysvnurl / myproject / tags / majorrelease_01

Answer 6

try reading this svn copy page. Basically you just need to backup svn

Answer 7

In CVS, this was called a "tag." SVN does not use a separate mechanism for tags; it simply creates a branch. So just create a new branch and give it a descriptive name like "release-1.2".

Alternatively, in a lazy way would be to write the current version number of the repository in a text file;)

Answer 8

Here is another useful idea. Use CruiseControl (or CruiseControl.NET) to automatically mark at fixed intervals (i.e. at night or every 15 minutes).

Get the build process now!