Use SemVer for packaging (eg. 1.2 should have been 2.0)

[leplatrem]

Version 1.2 was released with a number of breaking changes, breaking projects (eg. Kinto/kinto#2296)

(Drop support for Python 3.4, renamed the ZopeTransactionExtension class to ZopeTransactionEvents)

Would you mind following SemVer for following releases please?

[jugmac00]

"Drop support for Python 3.4..." dropped support for Python 3.4 - I know this as I reviewed the PR.

I guess you meant the PR just before: #34

[Natim]

I guess you meant the PR just before: #34

Indeed

[leplatrem]

I guess you meant the PR just before: #34

Well, the PR does not really have anything to do with the version picked during the release.
In this case I would say that this commit 1c2a56f is the one concerned.

Bumping major when a breaking change is part of a release is a recommended practice, but no big deal, we'll survive :)

[mgedmin]

Should we re-release 1.2 as 2.0?

[mgedmin]

And also we should add instructions for users about how they should adapt their code to the changelog, see #37.

[leplatrem]

Should we re-release 1.2 as 2.0?

I don't it's necessary. Just let's consider it for the next breaking change!

And also we should add instructions for users about how they should adapt their code to the changelog, see #37.

Yes, that would definitely be helpful!

[icemac]

As a re-release does not seem necessary, I am closing this issue as "won't fix".
Please reopen if needed.