-
Notifications
You must be signed in to change notification settings - Fork 51
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 #208
Comments
@xiki-tempula @DrDomenicoMarson what should be accomplished before we can release a 1.0? Those issues/PRs should be added to the 1.0.0 milestone. |
For 1.0.0, we need
We can leave PR #254 to a later date as it is not important. |
Sounds sensible. Could you please adjust the milestone tags as necessary, @xiki-tempula ? |
I think we need to have a somewhat definitive solution/workaround for issue #242 before 1.0.0, I'm waiting for a definitive response from AMBER developers. Tomorrow I'll better explain the situation in the relevant thread, and I'll try to propose a reliable solution! |
@DrDomenicoMarson The 1.0.0 is just to make the API stable. For #242, if it is too difficult, we could just do a 1.0.1. But it would be really helpful if this could be done before 1.0.0. |
I'm fine with a 1.0 release. As usual, I would imagine that 1.0.1 release will soon follow. |
The 1.0.0 release is now available. It should be on conda-forge within a day or so. @DrDomenicoMarson do you have a twitter handle so that I can give you some credit in the announcement tweet? |
Wow, that was quick :-) |
Thanks. I am still waiting for conda-forge https://github.com/conda-forge/alchemlyb-feedstock/ (there's an automated process that creates a PR from the PyPi package but it typically has a couple of hours backlog) |
Manually working on the cf package in conda-forge/alchemlyb-feedstock#6 |
Cf package for 1.0.0 is now available https://anaconda.org/conda-forge/alchemlyb/files |
All done, I even tweeted about it. |
Create a 1.0 release (we have a reasonably stable API).
Release management
The text was updated successfully, but these errors were encountered: