I'm using Glide as a dependency manager and I'm using a new feature (ShouldBindUri which I guess it has 30 days merged in Master), can you guys create a new version so we can use those new features?
Can't wait to have validator v9 in the new release :)
version 1.4 will be released on February 2019.
@thinkerou appreciate the work you're doing. I think this issue should perhaps stay open until you cut that release. I came here for same reason and had to go digging to find it.
hello, any update?
The milestone is due in a day or so https://github.com/gin-gonic/gin/milestone/9 fingers crossed!
@mikestead thanks! Due date is only an estimate. we still need to wait @javierprovecho come back.
Hello, any update?
Hello, any update?
Any update on this?
@javierprovecho @thinkerou @appleboy I am willing to help push this over the finish line if that is helpful.
We all looking forward to this release.
@thinkerou the vendor/vendor.json
versions I don't think are matching up with the go.mod
/ go.sum
files what is your thoughts for dealing with this? Are we dropping support for what ever was using vendor/vendor.json
this release?
@dmarkham need to update vendor/vendor.json
. gin1.4 need to support govendor because go module releases on go1.11.
@thinkerou so after taking a stab at getting the govender
to match go modules
I'm not yet able to to get go1.6
to work. The main reason is we have moved from versionv0.04
-> v0.0.6
of github.com/mattn/go-isatty
This package is now using the golang.org/x/sys/unix
pacakage that then uses runtime.KeepAlive
this is not in go1.6
. So This leaves us a few options.
github.com/mattn/go-isatty
go1.6
and go1.7
in gin 1.4.0
github.com/mattn/go-isatty
depending on your choice of dependency manager/go version. My preference is to drop go1.6
and go1.7
in 1.4.0
.
Thoughts?
Drop it cloud be a good choice as we're already in go version 1.12.
@thinkerou @appleboy do you guys have any feedback that we can use to move forward on this? or we planning just to hold off and wait for @javierprovecho?
Went ahead and merged in the removal of go1.6
/go1.7
#1851 in a new pull request as an option for @javierprovecho to review. Also fixing the simple merge conflicts.
@thinkerou @appleboy dont think that such a widely used repo should be blocked on merging improvements if @javierprovecho is away
@thinkerou and me don't have the permission to create new Tag and we must wait for @javierprovecho review all features and bugs.
so, can you contact with the author?
Yes @visamz Javier has been in contact. He is currently traveling. I do expect things to speed up a bit when he is back. I selfishly would like to have gin
a bit more nimble, but it is such a delicate balance between speed and stability.
I have done just a small amount of the grunt work for this release, but I have not setup for a gin release before, so all of the work needs to be checked/verified/corrected and may turn out not be helpful at all!
We already have so many new PR's ready for v1.5.0
killing me to have people waiting to get code merged in or explained why it will be rejected.
v1.4.0
should be here soon enough :100:
:wave: Guys, do we have an approximate date when master will be released?
Waiting
still waiting
emm... few months later.
:disappointed:
go.mod
feature allows you to specify a specific version, example:
module mymodule
go 1.12
require (
github.com/gin-gonic/gin master
)
This solved the version issue for me, Go 1.11 is required.
@appleboy @thinkerou @javierprovecho Hello Guys! Just a friendly reminder, we are all excited for a new release.
See the new release v1.4.0 https://github.com/gin-gonic/gin/releases/tag/v1.4.0
@thinkerou @appleboy Nice job guys I know it was not easy... Lets get rolling on 1.5.0
:+1:
Most helpful comment
Yes @visamz Javier has been in contact. He is currently traveling. I do expect things to speed up a bit when he is back. I selfishly would like to have
gin
a bit more nimble, but it is such a delicate balance between speed and stability.I have done just a small amount of the grunt work for this release, but I have not setup for a gin release before, so all of the work needs to be checked/verified/corrected and may turn out not be helpful at all!
We already have so many new PR's ready for
v1.5.0
killing me to have people waiting to get code merged in or explained why it will be rejected.v1.4.0
should be here soon enough :100: