v1.5.0

[methane]

I merged #943, which solves critical (race) issue #903.

@julienschmidt would you create a new release? Or may I do it?

Since the fix is just committed on master branch, I think it's safe to wait about week
to make new release. Some users will test master branch. So there will be feedback
if there is any regression.

[julienschmidt]

So far those minor releases were bugfix releases. We have some more changes since the last release. I'd say we make a (small) 1.5.0 release instead.

But I agree, we should tag a new release soon.

[sagikazarmark]

Is there an ETA for the new version?

[vmg]

Hi folks, any chances we could tag a new version of the driver? We've merged quite a few critical bugs since the previous version and no breaking changes. Tagging a new version would be important I believe.

[vmg]

Folks, it's been almost a year since the last minor release of the library. Please, could we tag a release with the many bugfixes that have landed in master since then?

[mbyio]

I see there are a few issues still included in the v1.5.0 milestone, but there are some features, like the ability to clone a config, which seem to be ready now. Is there any way we can do a release to at least get some of those features (and other bug fixes) out?

[Delphier]

When released?

[colega]

v1.4.1 was released a while ago here: 72cd26f

But it's not in master branch.

We're trying to pin this dependency to the latest master commit (15462c1) but golang understands that the latest master version is v1.4.0 and creates a pseudo version v1.4.1-0.20191121062641-15462c1d60d4 which is later replaced by other dependencies depending on v1.4.1 which is highet than the pseudo version. Since v1.4.1 is not in master, we can't point to a pseudo-version v1.4.2-0.20191121062641-15462c1d60d4 either because:

go: github.com/go-sql-driver/mysql@v1.4.2-0.20191121062641-15462c1d60d4: invalid pseudo-version: revision 15462c1d60d4 is not a descendent of preceding tag (v1.4.1)

Please, release the v1.5.0 or v1.4.2 to make latest changes available as dependencies.

(We know we can add a replace directive but that was our last solution)

[vmg]

@julienschmidt: It seems like all the maintainers for the driver have been very busy lately. Since I have time to work on this, and I have contributed most of the functionality/fixes that will be included in the release, would you like me to work on actually preparing the release any fixing any blockers we may have? Please let me know, this is a priority for us and I can allocate as much time as required to make the release happen. Thank you!

[methane]

@vmg Would you create a PR like #809?

[vmg]

Yes! I'll get to it ASAP.