<div>
<div class="content wysiwyg-content">
we have a repository with 1 branch and 1 trunk in SVN, working on the daily change on the branch and after a week or so we pass the changes into the trunk using tortoise merge and later we continue using the branch to make more changes and so on. this way we think that can save al changes while maintaing a stable realease to build.<br />
<br />
this way of working is recommended or we are wrong?<br />
<br />
regards
</div>
</div>


we have a repository with 1 branch and 1 trunk in SVN, working on the daily change on the branch and after a week or so we pass the changes into the trunk using tortoise merge and later we continue using the branch to make more changes and so on. this way we think that can save al changes while maintaing a stable realease to build.

this way of working is recommended or we are wrong?

regards

Best way to work with branches and trunks in SVN

Version control, also known as revision control or source control, is the management of changes to documents, computer programs, large web sites, and other collections of information. Changes are usually identified by a number or letter code, termed the "revision number," "revision level," or simply "revision." Version control systems (VCS) most commonly run as stand-alone applications, but revision control is also embedded in various types of software such as word processors and spreadsheets, and in various content management systems. Revision control allows for the ability to revert a document to a previous revision. Git, a widely-used VCS, has its own topic; other popular systems include CVS, Subversion, Team Foundation Server (TFS), Visual SourceSafe (VSS) and Perforce.