3 ms·
This isn't good general advice. The vast majority of projects aren't going to need to cherry pick commits to such old branches, and overly limiting style fixes
by spankalee 5y ago
This isn't good general advice. The vast majority of projects aren't going to need to cherry pick commits to such old branches, and overly limiting style fixes and refactorings is a good way to ossify a code base.
- cypressious 5y agoThis is exactly what the author is saying in the final paragraph.
- sharken 5y agoThe same problems exist when you merge between multiple release branches, there is an inherent resistance to refactoring as it interferes with merges. To me the solution is to migrate to trunk based development and hide new features behind feature flags. The biggest issue with this transformation seems to be implementing feature flags in the code.