version control

This is regarding SVN branching strategy- What is harm in deleting trunk and copying branch to trunk to reflect production code which was delivered from Branch.

It is known that history on trunk will be lost however history on the repository still exist and any file at any revision can be recovered. So what would be issues with deleting trunk and recreating trunk from branch.

Hi everyone,

What is the workflow of a code release using SVN? Do the developers cut a tag every time they need to push some code to production?  Right now we use CVS and the developers request code change through a request form which scans for files and the versions. They select the files and request a code change. The release enginner starts with the file names and their versions, checks out and releases to test and prod. How can I achieve something like this in SVN. since SVN uses global revision numbering system I would like to know if developers request the entire repository after creating a tag or do file based?

While source code version control has been a staple of basic software configuration management (SCM) in most development projects for decades, databases have been largely ignored. Implementing SCM principles in database development gives objects protection and enables the automation of database deployments. Software can help to facilitate these processes, but database SCM practices should be instilled from the top of the development organization in order to ensure optimal benefits.

For years, developers have struggled with using individual lifecycle management tools, but no longer! Joe Farah walks you through a history and benefits of an integration of ALM tools that every team should seriously consider.