Software Development Cross Solution - Index of - Free

tagging revisions
(Emergency) standup meeting
204 Chapter 6
1.
2.
3.
If you’re having a problem, don’t wait for
the next day. Just grab everyone and
have an impromptu standup meeting.
Laura: We could check out the version 1.0 code just fine, but now
the version control server won’t let us commit our changes back in.
It says our file is out of date.
Mark: Oh—ya know, that’s probably a good thing. If we could
commit it, wouldn’t that become revision 6, meaning the latest
version of the code wouldn’t have Bob’s changes?
Bob: Hey that’s right—you’d leapfrog my code with old version 1.0
code. I don’t want to lose all of my work!
Laura: You still have your work saved locally, right? Just merge it in
with the new changes and recommit it. You’ll be fine.
Bob: Uggh, all that merging stuff sucks; it’s a pain. And what about
the next time we find a bug we need to patch in Version 1.0?
Mark: We’ll have to remember what the new 1.0 revision is. Once
we figure out how to commit this code, we’ll write down the revision
number and use that as our base for any other 1.0 changes.
Laura: New 1.0 changes? Wouldn’t we be at Version 1.1 now?
Bob: Yeah, that’s right. But this is still a mess...
Write down three problems with the approach outlined above for
handling future changes to Version 1.0 (or is it 1.1?).
Download at WoweBook.Com
Answers on page 217.