maximbaz
commented
6 years ago To follow-up on this, first of all thanks @keegancsmith for tagging v2.0.0 soon after I opened this ticket, as you can see by the number of upvotes this is truly important for other people.
After seeing the release tagged I feel encouraged now to create a package for Arch Linux and I will do so, I would only like to confirm with you guys that you are planning to tag new releases on frequent basis. I'm asking because in my mind having an "official" package that is based on very old source code is worse than having no package at all, I don't want to give people a false sense of trust that this package is recommended for use unless the developers commit to keep tagging new releases.
Hello, I'd like to create a
go-langserverpackage for Arch Linux, but such package needs to follow official releases.I've noticed that
go-langserver -versionis a thing and there even are instructions in the source code:https://github.com/sourcegraph/go-langserver/blob/7df19dc017efdd578d75c81016e0b512f3914cc1/main.go#L39-L44
I would highly recommend following semantic versioning:
For packaging purposes all I need is a tagged commit, Github and I will do the rest,
-versionflag is a nice bonus if you can keep it up to date.I'm making this package so that it's simpler for people to install your tool and update it as time goes by. I would also like to ask you to keep making releases often, so that users actually benefit from following official releases.
I'd like to highlight that by making official releases you are not binding yourselves to support old versions, it is perfectly valid to ask users to upgrade. On the contrary, you will start seeing a version in bug reports, and hopefully it will help you triage some issues faster.
Let me know if you have some questions or concerns.