|
I agree that from an i point of view there needs to be some Master Copy
stored in an i library. But in my thought - and I believe that is also the
Subversion idea - this master copy should always be an SVN working copy,
which is checked out from the repository from a tagged release. Not every
repository revision should be synchronised immediately to this master copy.
Imagine that you have your Master Copy checked out just from a tagged
release, say you tagged it as version 1.24, which is for example at level of
revision number 1540. Another developer has also checked out a working copy
of the trunk to his own IDE, and has worked on some source code. When he
commits this code (maybe in two or three commits 1541,1542,1543) you don't
want to have this code immediately applied to your Master Copy. That would
break a good release management. Instead of doing so, you should look
carefully what the changes in these revisions are, and if it is okay then
for example you will tag revision 1543 as the new production release 1.25.
That is much safer and more conform the Subversion philosophy than let
everybody digging around in your master copy.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.