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?
Thanks Bob. Sorry for late response. I somehow missed your reply.
Yes, I am working in Finance. Please share more insight on a code release workflow. I can't find any articles regarding this. I am looking for specific examples. We have a mix of standlone scripts as well as Java/Flex application type projects
most of us do indeed use a tag in SVN (or most other version control systems) to baseline a release. Now the requirements for baselining are generally impacted by the type of business that you are in and the commonly accepted requirements or regulatory requirements. Are you working in finance, banking, medical or some other industry?
Thanks Bob. Sorry for late response. I somehow missed your reply.
Yes, I am working in Finance. Please share more insight on a code release workflow. I can't find any articles regarding this. I am looking for specific examples. We have a mix of standlone scripts as well as Java/Flex application type projects