You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Go's Vendor Packaging now approaching maturity do you think there is any value in using Git to assign a Version Number to gofreetds ?
For my work projects I am introducing the use of Glide, which let's me pin a build dependency to a specific Go package version (be it a Git tag, a commit checksum, etc). This let's me generate reproducible builds over different machines and eases CI.
Time for a gofreetds 1.0.0 ? :-)
Alternatively, could gofreetds start using gopkg.in ?
The text was updated successfully, but these errors were encountered:
With Go's Vendor Packaging now approaching maturity do you think there is any value in using Git to assign a Version Number to gofreetds ?
For my work projects I am introducing the use of Glide, which let's me pin a build dependency to a specific Go package version (be it a Git tag, a commit checksum, etc). This let's me generate reproducible builds over different machines and eases CI.
Time for a gofreetds 1.0.0 ? :-)
Alternatively, could gofreetds start using gopkg.in ?
The text was updated successfully, but these errors were encountered: