Tag new release

[falzm]

Hi

Could you please tag a new release for your package? The v1.0.0 is more than 6 months old, using Go modules automatically pulls the latest tagged version of the module (there's a workaround for that, but it's not convenient) – and quite a lot of code is missing, compared to the online documentation which is based on master.

Thank you in advance!

[aboch]

👍

[onlyjob]

Due to lack of fresh release various projects already had to deviate from vendoring by tag...
Please, pretty please consider tagging a release for the sake of best practice.
Thanks.

[vishvananda]

@aboch seems like we should go ahead and do a 1.1.0 release?

[onlyjob]

Yes please. :)

[guesslin]

@vincentbernat hi, is there any news about the new release tag? I'd like to import this codes, but with v1.0.0 is mid of 2018, and it's end of 2019 (there're almost 100 commits not included in the fresh tag)

#424 (comment)
This is also a problem for those who using go mod.

Please consider tagging a new release.
Thanks

[gustavo-iniguez-goya]

Hi all!

@vishvananda do you think you could tag a new release? I'd like to use the new feature recently added e499154 (SocketDiagTCPInfo). As far as I can tell works fine.

It's almost 1 year since last release.

[fach]

@aboch Would you folks mind tagging a new release? I'd like to use the work added in #585 without having to use a commit hash.

[AkihiroSuda]

@vishvananda Could you consider creating a new release? 🙏 The latest release v1.1.0 is more than 2 years old.

Just creating a beta tag like v1.2.0-beta.0 might suffice for most people.

[vishvananda]

I've tagged a beta release. Please try it out and let me know if there are any issues and i'll upgrade it to an official 1.2.0

[dfateyev]

Probably, it's worth to tag a new beta / RC?

[aboch]

https://github.com/vishvananda/netlink/releases/tag/v1.2.1