• Clément JolyOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    That’s a good point. However, if it is the case that the most popular plugins are the ones predominantly introducing disruptive breaking changes, then you just need these plugins to follow the proposal. And then, you get control over, say 80% of the disruption, even with relatively limited adoption. In my experience, these popular extensions tend to have a fairly thorough readme, even wikis and community discussions sometimes, so they might be keener to also follow this kind of practices.

    Case in point, telescope.nvim even has releases, so they clearly care about providing more stable snapshots.

    • Clément JolyOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Further reading the telescope release notes:

      With this release we also introduce a new release branch 0.1.x which will get constant fixes, performances improvements and new features without breaking backwards compatibility, so we kindly ask you to switch to either the fixed 0.1.0 tag or this release branch.

      Seems relatively close to the proposal.