Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

17.1.0 #213

Merged
merged 1 commit into from Aug 15, 2017
Merged

17.1.0 #213

merged 1 commit into from Aug 15, 2017

Conversation

IlyaSkriblovsky
Copy link
Contributor

I believe that quick fix from #211 deserves a release because simple pip install txmongo results in broken installation right now (since it installs txmongo 16.3.0 and pymongo 3.5.0 which are not compatible).

Should we name the new release 17.1.0? Or may be 16.3.1 because it consists only of bugfixes?

I believe that quick fix from #221 deserves a release because simple `pip install txmongo` results in broken installation right now since it installs txmongo 16.3.0 and pymongo 3.5.0 which are not compatible.

Should we name the new release 17.1.0? Or may be 16.3.1 because it consists only of bugfixes?
@psi29a
Copy link
Contributor

psi29a commented Aug 11, 2017

Go ahead for 17.1.0... we have enough material. It is a good idea anyway, new release of the year that we're half-way through.

@coveralls
Copy link

coveralls commented Aug 11, 2017

Coverage Status

Coverage remained the same at 95.194% when pulling fa69055 on 17.1.0 into b1191c7 on master.

@IlyaSkriblovsky
Copy link
Contributor Author

IlyaSkriblovsky commented Aug 14, 2017

So, could you please merge this if you don't have objections and publish the new release to PyPI? Thanks!

@psi29a psi29a merged commit c5ee3b4 into master Aug 15, 2017
@psi29a
Copy link
Contributor

psi29a commented Aug 15, 2017

pushed...

https://pypi.python.org/pypi/txmongo

@IlyaSkriblovsky
Copy link
Contributor Author

IlyaSkriblovsky commented Aug 15, 2017 via email

@IlyaSkriblovsky IlyaSkriblovsky deleted the 17.1.0 branch August 16, 2017 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants