Software Development Cross Solution - Index of - Free

3
The fix is in
the branch.
...and commit our changes back in. This time, though, no conflicts:
File Edit Window Help Sweet
hfsd> svn commit src/headfirst/sd/chapter6/BeatBox.java -m “Fixed the
critical security bug in 1.0 release.”
Sending src\headfirst\sd\chapter6\BeatBox.java
Committed revision 10.
hfsd>
We have TWO code bases now
With all these changes, we’ve actually got two different sets of code: the
1.x branch, where fixes are made to Version 1.0, and the trunk, which has
all the new development.
Our trunk directory in the repository has the latest and greatest code
that’s still in development (and Bob applied the security fix there, too).
We have a version-1.0 tag in our tags directory so we can pull out
Version 1.0 whenever we want.
We have a version-1 branch in our branches directory that has all
of our critical patches that have to go out as a 1.x version without any
of the new development work.
Download at WoweBook.Com
version control
Don’t forget: when you actually
do release v1.1 with these
patches, create a version-1.1 tag
in the tags directory so you can
get back to that version later if
you have to.
you are here 4 209