-
Notifications
You must be signed in to change notification settings - Fork 7
Ready for v0.1.1 PyPI/GitHub release #31
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
Comments
Thanks @cadenmyers13 please ping me again when all the items are completed. |
@bobleesj Following the README, when I install with |
@cadenmyers13 for conda-forge, yes. We currently have it under the |
@cadenmyers13 I changed this to |
@cadenmyers13 I added issues that we want to close on this release to the 0.1.1 release milestone. |
Could you please setup codecov token for ![]() |
OK, not sure how to do this. I thought I configured it correctly and added the |
@cadenmyers13 Just to note the codecov badge works. Thanks @sbillinge! |
@sbillinge Can I get a verification that the licensing is correct for this package? |
yes, can confirm. I checked that on the list. |
@sbillinge @bobleesj Once the opened PRs are confirmed and merged we should be good to release |
in other words, we are not ready for release. Please let me know when we are..... |
All issues and PRs associated with package content have been closed and content is up to date with current cookiecutter standard. New issue (#65) has been created for support of python 3.13. |
@cadenmyers13 Please provide a bit more context on why this issue is closed while we have a checklist for 0.2.0 being created. #65 (comment) I recall 0.1.1 was simply for recutting and 0.2.0 would be recutting + supporting py 3.13 |
comment has been updated^ |
Closed as completed. |
Release checklist for GitHub contributors
missing), tutorials (no tutorial in
diffpy.fourigui
, and other human-written text is up-to-date with any changes in the code.Please mention @sbillinge when you are ready for release. Include any additional comments necessary, such as
version information and details about the pre-release.
The text was updated successfully, but these errors were encountered: