Announcing Backport Policy

[NotAShelf]

Hey all,

It has come to my attention that there is a more-than-marginal number of people who are pinning the "stable" branches of nvf (and therefore Neovim), which usually do not get any attention from us maintainers. This was never recommended, but I understand that some users will be much less likely to desire to have a bleeding edge Neovim configuration. To aid those users, I am beginning an initiative to backport changes made to the main branch to the latest stable branch. This policy will be effective once 0.8 is released and tagged, and changes made to the main branch (which will be 0.9-unstable) will be backported as they are suitable. Of course, large changes will be less likely to be backported, but the latest (and only the latest) stable branch should remain up to date for those interested.

Chances are, 0.8 changes will not be backported to 0.7-stable, as 0.8 contains a large Neovim update that allowed us to change how LSPs work. If you have not yet updated to 0.8, I encourage you to switch at your earliest convenience. The current API has not been revised to support < Neovim 0.11 properly, and likely will not be in the near future.

Cheers!

[inayet]

Thank you for thinking of those people who like to be on stable branches. I love the fact that you are focusing on the latest code I wish there was a way where everything was like up to date and like every single dependency you know were updated on autopilot but I'm sure that might not be possible today but I just love it and thank you for making it and building it to be that way when it is possible