Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

9. Release Codelines > 9.6. Breaking the Rules

Breaking the Rules

Despite the most meticulous planning, we occasionally have no choice but to defy the rules of the codeline road. In this section we’ll look at two ways to break the rule that says change does not flow to a release codeline from its parent.

Backporting a bug fix

When you’re supporting several releases at once, you may find yourself in a situation where a bug fix made in one release has to be backported to another. For example, Jody, of Ace Engineering’s QA team, has detected a subtle but severe, data-corrupting bug during stabilization of the REL2 codeline. Ann, a developer responsible for the module in which the bug was found, fixed the bug in REL2 with changelist 8896. She then merged her fix to MAIN, using the procedure described in "Integrating Changes into the Mainline,” earlier in the chapter. Change 8904 is the point at which REL2’s change 8896 was incrementally integrated to MAIN. (The fact that the change was integrated incrementally is what’s going to make this bug fix easy to backport.


  

You are currently reading a PREVIEW of this book.

                                                                                                                    

Get instant access to over $1 million worth of books and videos.

  

Start a Free 10-Day Trial


  
  • Safari Books Online
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint