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
Release 1.0.0 #410
Comments
I'm happy with completing the conversion to pytest and getting 1.0.0 out the door! |
#334 👌 Am I right that we are not getting coverage comments any more in the PRs? According to my local check it's still at 96%. |
Looking through the remaining Other than that there are a few modules left that use unittest:
Additional notes: |
|
|
|
Any other bugfixes that should get in? Perhaps #405? |
Apparently #405 breaks on Python 3 https://travis-ci.org/audreyr/cookiecutter/builds/53786422 |
There are still some PRs open for the milestone:
|
Okay, everything is either merged in or pushed to the 1.1.0 release. I am commencing the 1.0.0 release! |
Working through https://gist.github.com/pydanny/940641f591198c78b8a4 |
Great! 😄
Can we possibly change the description in Lay the foundation for py.test fixtures and convert test_generate.py and test_examples.py to something along the lines of Convert the unittest suite to py.test for the sake of comprehensibilty I'm sure you'll come up with something better than this. I'm basicly sleeping already 😪 |
@marctc is linked properly now. Also changed the |
Thank you, Sir! 🙇 |
+1 |
I would like to close out this release cycle in the next few days. If there are any bug fixes (no features!) that really should get in, please list them in the comments.
The text was updated successfully, but these errors were encountered: