5 ms·

A Tale of Two Commits (2018)

• kazinator 8y ago
  Splitting patches so change topics aren't mixed together: important at Mozilla. Not breaking thousands of browser extensions in one release: not so much.
  • labster 8y ago
    I'm so tired of hearing about this. XUL was slow, and no one wanted Mozilla to spend millions improving a standard of which it was the sole user. There was a multi-year deprecation cycle. Everyone had a chance to update in advance. Sorry your workflow was broken, but sometimes the users have to pay the price for technical debt too.
    • deleted 8y ago
      [deleted]
• gumby 8y ago
  We use "squashed diff" so you get a single patch for a single fix or stable portion of a new feature (a whole new feature if it's small & nonbreaking). I would think the "trickle of small changes" would be painful to keep track of, especially on a large team.