• Zach 🇮🇱 🇺🇸@fosstodon.org
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    2 days ago

    @kurushimi @cm0002 From what I understand, Kent Overstreet has attempted to circumvent the release cycle by adding #features to an #RC, which was the final straw. #Linus (Torvalds) has warned him repeatedly, but it wasn’t just him. Based on a comment I read from one of the #kernel #developers, his repeated #antics made it considerably more #difficult for them to complete their #work. So while #technically you might be right, it’s not that simple.

    • BCsven@lemmy.ca
      link
      fedilink
      arrow-up
      15
      ·
      2 days ago

      Yep the maintainer repeated threw in stuff late in the release cycle . Here’s one instance

      The clash stems from a long‑standing debate on kernel rhythm: Linus enforces strict release-cycle discipline, allowing only minimal fixes during release candidates.

      At the same time, Kent submitted substantive changes (a patch implementing the new “journal_rewind” feature, which lets the entire filesystem be reset to an earlier point in time) justified by urgent data-recovery needs, though they landed late in the cycle.

    • kurushimi@sh.itjust.works
      link
      fedilink
      arrow-up
      6
      ·
      2 days ago

      For sure. And it wasn’t that simple during the rust shenanigans in February I’d say, but these personalities love to come up and cause trouble 😅. It’s really the nature of open source though; you’ll find similar in major open source projects. Hashicorp GitHub issues come to mind as an easy example.