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

release 1.0 #208

Closed
6 tasks done
orbeckst opened this issue Jul 23, 2022 · 12 comments
Closed
6 tasks done

release 1.0 #208

orbeckst opened this issue Jul 23, 2022 · 12 comments
Assignees
Labels
Milestone

Comments

@orbeckst
Copy link
Member

orbeckst commented Jul 23, 2022

Create a 1.0 release (we have a reasonably stable API).

Release management

  • updated CHANGES
  • tagged 1.0.0
  • checked testpypi version
  • created release on GitHub
  • created conda package (reviewed and merged the cf-regro commit to the conda-forge repo for the conda package)
  • announced in forum
@orbeckst orbeckst self-assigned this Jul 23, 2022
@orbeckst orbeckst mentioned this issue Jul 23, 2022
6 tasks
@orbeckst orbeckst added this to the 1.0.0 milestone Jul 23, 2022
@orbeckst orbeckst mentioned this issue Aug 17, 2022
4 tasks
@orbeckst
Copy link
Member Author

@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.

@xiki-tempula
Copy link
Collaborator

For 1.0.0, we need

We can leave PR #254 to a later date as it is not important.

@orbeckst
Copy link
Member Author

Sounds sensible. Could you please adjust the milestone tags as necessary, @xiki-tempula ?

@DrDomenicoMarson
Copy link
Contributor

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!

@xiki-tempula
Copy link
Collaborator

@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.

@xiki-tempula
Copy link
Collaborator

I'm fine with a 1.0 release. As usual, I would imagine that 1.0.1 release will soon follow.

This was referenced Oct 31, 2022
@orbeckst
Copy link
Member Author

orbeckst commented Nov 1, 2022

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?

@DrDomenicoMarson
Copy link
Contributor

Wow, that was quick :-)
My Twitter handle is DomenicoM87!

@orbeckst
Copy link
Member Author

orbeckst commented Nov 1, 2022

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)

@orbeckst
Copy link
Member Author

orbeckst commented Nov 2, 2022

Manually working on the cf package in conda-forge/alchemlyb-feedstock#6

@orbeckst
Copy link
Member Author

orbeckst commented Nov 2, 2022

Cf package for 1.0.0 is now available https://anaconda.org/conda-forge/alchemlyb/files

@orbeckst
Copy link
Member Author

orbeckst commented Nov 2, 2022

All done, I even tweeted about it.

@orbeckst orbeckst closed this as completed Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants