|
Chris, I use Subversion all the time at work and can tell you what happens here. When a new project is created there is only the head to code on, all new work is always done on the head. Once a project gets to a version (minor or major) it's tagged. Mostly tags are used for major releases like a version 1.0 but they could easily be for a version "1.1 bug fix". These tagged versions allow us to checkout a project as live production and if a problem arises check back out that exact version. It also tells us that at this point the code was at a functioning state. One thing you can do is if you are bug fixing production code is to make a fork from the tagged version. This splits the source into a separate development area that doesn't interfere with the current development work at the head. After the bug has been fixed on the fork you can merge it into the head. Hope this helped. Robert |
_______________________________________________ Reply to DFWCFUG: [email protected] Subscribe/Unsubscribe: http://lists1.safesecureweb.com/mailman/listinfo/list List Archives: http://www.mail-archive.com/list%40list.dfwcfug.org/ http://www.mail-archive.com/list%40dfwcfug.org/ DFWCFUG Sponsors: www.instantspot.com/ www.teksystems.com/
