Mysql: Semantic Versioning

Created on 23 Aug 2016 · 7Comments · Source: go-sql-driver/mysql

The last version to be released was v1.2 on Jun 3, 2014. There have been nearly 200 commits to master since then. Tools such as Glide and gopkg.in use these tags to satisfy semantic versioning constraints.

Could you please publish a new release/tag with the appropriate version (depending on whether or not backwards compatibility has been broken or new features have been introduced). Otherwise, if there is some reason you have not published a release in a while, would you mind clarifying?

organization

Source

albrow

Most helpful comment

@julienschmidt thanks for the response. I look forward to the v1.3 release.

Still, don't you think that more than 2 years and 200 commits is too long to go without even a patch release? Developers who use semantic versioning will not be getting any of those changes. Typically, one would release regular patch releases (e.g. v1.2.1) whenever there are changes so that users will receive updates.

albrow on 29 Aug 2016

👍2

All 7 comments

See Milestone v1.3
v1.3 will be tagged when these issues are fixed.

julienschmidt on 24 Aug 2016

@julienschmidt thanks for the response. I look forward to the v1.3 release.

albrow on 29 Aug 2016

👍2

We will start using semantic versioning after the v1.3 release.

julienschmidt on 25 Oct 2016

👍1

Tagging a new release with every merged pull request is not an option.
The question is when we release those minor versions then?

julienschmidt on 16 Nov 2016

I feel bad bumping such an old issue - but this is clearly not resolved yet. The 1.3.0 release was over a year ago, and unless this project is targeting a release cadence over twice as slow as the language it is built in, this hasn't been dealt with organizationally yet.