search

daa84 / neovim-gtk

gtk ui for neovim
GNU General Public License v3.0
716 stars 57 forks source link

New release #188

Closed XVilka closed 5 years ago

XVilka commented 5 years ago

There are already many changes since the last release - it makes sense to tag a new one.

alerque commented 5 years ago

Wow yes please I had no idea there had been so much development since the version on my system was released!

daa84 commented 5 years ago

Not sure somebody use this tag for releases, but if this is important i can create new release

unclechu commented 5 years ago

@daa84 Yes, that would be great. And it also would be great if you add some changelog info between future releases.

alerque commented 5 years ago

Just to confirm @daa84, this is important. Most distributions rely on upstream projects' tags to package software. For example Archlinux has a package in the AUR for neovim-gtk. That is what most of my systems have and what I think of as the current state of the project. This assumption will be true for most people. There is a neovim-gtk-git package as well, but ⓐ most distros do not have alternative packages for upstream HEAD versions like Archlinux sometimes does and ⓑ these are generally not people's go-to versions. The assumption is that -vcs HEAD versions may or may not work at any given time and the tagged version should always be a know-working condition. Personally I tend to only install -vcs versions of packages that are software I personally contribute to and follow the development process on and will know when not to update my system packages.

Obviously everyone will have their own style, but the last tagged release is the thing that your project will be known for. If lots of good development has happened since a tagged release and you think people should be using it rather than the old version, then tag a new release. Don't limit your project's exposure to only brave souls who build their own packages from upstream HEADs.

daa84 commented 5 years ago

New release tagged.