Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • What are 'release breaks'? Commented Jan 18, 2013 at 7:25
  • A small pause in development till trunk is stabilized to create a release! This may or may not be significant depending on the maturity of the developers. Commented Jan 18, 2013 at 7:28
  • 2
    I don't buy the 'release breaks' argument. It seems to me that that is a problem with your branching rather than CVCS as a concept. Commented Jan 18, 2013 at 14:39
  • +1 @James. My group was used to "release breaks", or "code freezes", when we used a seriously out-of-date version of PVCS. We've moved to TFS (most definitely not a DVCS) and use branches, not "breaks", to stabilise releases. It's hard to break the devs of thinking about a "code freeze" for each release, though. Commented Jan 18, 2013 at 17:23