-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.2 release timeline? #207
Comments
Same goes for dep. It tries to stick to latest tag by default. |
We also got a few bug reports in the past because our library sticks to your master version and more and more people use dep which by default takes the latest tag. Any plans for a new release? |
Same question from me :) I am trying to build Linkedin's Burrow with Debian Sid's golang-github-julienschmidt-httprouter-dev (that is still stuck at the 1.1 tag) and it fails since so many things have changed in the meantime. A 1.2 release would probably also kick off a new debian sid version that would be really appreciated! Thanks in advance! |
I'll chime in on this one too. With dep taking off, and vgo around the corner, tagging a new release every now and then is key to keeping people up to date. |
+1 I've realized that one of our projects is using |
+1 |
This comment has been minimized.
This comment has been minimized.
See #249. Tagged a new release. |
) Bumps [google.golang.org/protobuf](https://github.com/protocolbuffers/protobuf-go) from 1.26.0 to 1.27.1. - [Release notes](https://github.com/protocolbuffers/protobuf-go/releases) - [Changelog](https://github.com/protocolbuffers/protobuf-go/blob/master/release.bash) - [Commits](protocolbuffers/protobuf-go@v1.26.0...v1.27.1) --- updated-dependencies: - dependency-name: google.golang.org/protobuf dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Hi, is there a timeline for the release of 1.2? I see there are still a few outstanding commits on the milestone, but
1.1
points to a commit about two years old. Users of dependency managers like glide will likely pin their dependency onhttprouter
to the latest release (1.1
) and get a very old version ofhttprouter
.Is it reasonable to either finish the
1.2
blockers soon or push them to a later release?The text was updated successfully, but these errors were encountered: