This is done via the hook scripts, which enforce the immutability by preventing further changes if tag is a parent node of the changed object. It is very common for a typical Subversion repository implementation to treat any path containing "/tag/" to be write-protected after creation the net result is that tags, once created, are immutable (at least to "ordinary" users). Subversion allows sysadmins to create hook scripts which are triggered for execution when certain events occur for instance, committing a change to the repository. The branch and tag subtrees are distinguished from the trunk in the following ways: In open source projects, major branches that are not accepted into the trunk by the project stakeholders can become the bases for forks - e.g., totally separate projects that share a common origin with other source code.
#SUBVERSION MEANING SOFTWARE#
The two main reasons for preservation would be that either this is a major release of the software, whether alpha, beta, RC or RTM, or this is the most stable point of the software before major revisions on the trunk were applied. Tag will be a point in time on the trunk or a branch that you wish to preserve. If the major changes work according to plan, they are usually merged back into the trunk.
Trunk would be the main body of development, originating from the start of the project until the present.īranch will be a copy of code derived from a certain point in the trunk that is used for applying major changes to the code while preserving the integrity of the code in the trunk.
Hmm, not sure I agree with Nick re tag being similar to a branch.
0 kommentar(er)
