-
Notifications
You must be signed in to change notification settings - Fork 36
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 v1.0.0 #253
release v1.0.0 #253
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm very happy with just finishing those last 3 issues and calling it 1.0.0.
The package is passing all checks! https://cran.r-project.org/web/checks/check_results_uptasticsearch.html And binaries have been built by CRAN for all the platforms it supports 🎉 I just updated |
This happened in these PRs: |
put up the new release + tag: https://github.com/uptake/uptasticsearch/releases/tag/v1.0.0 |
Updated the dev version via #255 And with that, we are fully done with this release! @austin3dickey from this point forward, if I come back and push more PRs here, I'll go back to waiting for a review and not using admin powers to merge. Thanks for your help getting this release up! |
I think we're just about ready for a 1.0.0 release!
Release checklist
Before merging:
R CMD check
) on this branchcran-comments.md
on this branch once the package is (hopefully) accepted and passing checksconda-forge
recipe (https://github.com/conda-forge/r-uptasticsearch-feedstock)After merging:
main
asv1.0.0
1.0.0.9999
Notes for Reviewers
@austin3dickey , any other types of changes you think we should make before doing a new release?
And are you ok with going to the 1.0.0 version? I'm thinking this project's API is about as "stable" as it can get (not changed in the last 6 years, unlikely to change in the next 6 years 😅 ).