Switch to SemVer? about feline.nvim

[famiu]

If we do decide to go with Semantic Versioning, the way I'm thinking of doing it is by following the Git Flow workflow. For those who don't know what that is, that's how it works:

We add a develop branch and use it for rapid development while master remains only for stable, tested releases. People could use the develop branch if they wanted to but no stability would be guaranteed for those using it, whereas stability would be guaranteed for the master branch. Once we have enough features in the develop branch for a new version and have tested them enough, we fork a feature branch off of develop and eventually merge it on masters. Hotfixes may still be merged directly to master. I believe this'd allow us to:

1. Develop without worrying too much about messing up, since develop doesn't guarantee stability, we could change commits or rewrite history at anytime or improve features further before merging them.

2. Have meaningful version names and allow users to not accidentally install breaking changes.

3. Deprecate or remove features in the "API" without worrying too much about breaking existing userspace.

But I'm still wondering if it's worth it since at the end it's still just a Neovim plugin and Semantic Versioning is not the standard for Neovim plugins (yet).

[famiu]

I've decided that it's worth making the switch to semver and will be doing so very soon. The issue will be closed once that's done

[famiu]

Feline has now officially switched to SemVer, and so I'm closing this issue