Forum Post: RE: Best (or even common) practice on dev across multiple versions: branch vs...

  • Thread starter Thread starter Thomas Mercer-Hursh
  • Start date Start date
Status
Not open for further replies.
T

Thomas Mercer-Hursh

Guest
The issue I was trying to make with respect to upgrades is that if one has a customer population which one can keep reasonably current, like just 2 or maybe 3 versions at a time, then one of the virtues of branches is that when one leaves behind a particular version, one can simply abandon those branches and the code is essentially automatically cleaned of the version kludge. Whereas, if one has proversion tests and the like buried in the code, they are likely to persist long past where they are needed.

Continue reading...
 
Status
Not open for further replies.
Back
Top