> I'm currently thinking about migrating from CVS to SVN, since SVN > is said to be the successor of CVS. > When analyzing the differences between CVS and SVN I found tags are > treated in a different way in SVN, than they were treated in CVS, > because the tag concept in SVN is: A tag is just a "snapshot" of a > project in time. > This differs somewhat from the CVS concept of a tag: "You can use > the tag command to give a symbolic name to a certain revision of a > file." > We use tags in CVS to identify the files which have passed module > tests and should make it into our integration test environment.
So you are saying you test "files" in isolation? That seems a bit unusual I think. In svn you use a "tag" to give a symbolic name to a certain revision also. It's really not all that different. > When they have passed the integration tests we use a different tag > to identify the files, which make up the software in/for our > production environment. In addition to that our development model > is not release driven. As a result we do not tag the HEAD of our > complete source tree at a particular point in time. As soon as we > have finished development of a feature or functionality we tag the > files which have been changed with a tag named "Q". In a different > workspace we check out the "Q" tagged source tree. This gives us > the possibility to go on developing a feature while doing the > integration test on a previous revision of it and have a source > tree which consists of files, which reached the state of being > ready for integration tests or for production at different points > in time. In my opinion branches would be too complicated to achieve > the same functionality. > Does anyone have an idea how to achieve this flexibility and ease > of use with branches in SVN? What you described above is exactly what branches are for. Why do you think this would be complicated? This is exactly the description of a branch for release use case. I think you are over thinking this... how is tagging a revision that contains the changes for a feature with a "Q" than tagging each file with a "Q"? BOb
