Tag new release

[cpuguy83]

The last release was tagged a year ago.
I'm not sure what the current state of the repo is wrt API changes but was wondering if we can get a new tagged release?

Users are reporting a deadlock that is supposedly fixed on master but not in any tagged release: moby/moby#35332

If it's safe to take master I can just take that but figured it would be worth checking if there can be a new tag.

Thanks! 🙇

[thaJeztah]

ping @markbates @nathany ptal 🤗

[markbates]

I agree a new version is probably warranted. I don't have the insight into the package to determine if that's ok or not. @nathany is probably in the best position to make that call.

[thaJeztah]

Thanks! I'll await @nathany's input 👍

[nathany]

Sounds like a mighty good idea, though I have no insight into what has changed since the last release, or if it's "safe" to tag a new release.

As per my comment here, I haven't been following the project since March.

[thaJeztah]

Ah, I see (apologies; haven't really followed this project myself, only arrived here because of the linked issue); number of changes since March isn't huge; v1.4.2...master

Let me look around as well if there's maintainers, or contributors in the Moby project that would be able to help out on this project

[nathany]

Thanks @thaJeztah.

Unfortunately I haven't gotten around to #201 to describe how releases have been done in the past. Not that the process couldn't be modified to suit whoever takes up the baton. 😉

[nathany]

Should we also suggest the use of dep for the next release? https://github.com/golang/dep

It may not change the actual release process beyond initial updates to the README.