-
Notifications
You must be signed in to change notification settings - Fork 49
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
new release 0.2.0 #53
Comments
I'd also like to remove the "alpha state" warning
Some of us are using alchemlyb in a production environment already and the tests and docs are reasonable. Instead I like to add something along the lines that we welcome user input, especially in the form of bug reports, feature requests, and questions and that they should please use the issue tracker. I would also say that the library is still in development; our releases use semantic versioning so that users can immediately see what is happening in a release. I'll also start a CHANGELOG. |
- removed all references to gitter - added Contributing section and links to some of our wiki pages
* doc update (see #53) - removed all references to gitter - added Contributing section and links to some of our wiki pages * updates for docs for Amber parsers
@vtlim do you want to comment on timing for NAMD parser? This is really "no pressure" -- we're not in a rush to have it in, so we're interested in knowing when you think you would be likely to get to it, and NOT trying to apply pressure to get it done. |
I will plan to get to it later this week or next. I'll first take a look at the GROMACS or other parsers present to figure out how I need to morph mine accordingly. |
The release is blocked on
We can ship something without the NAMD parser #7 so I removed it from the milestone. |
Everything is ready for a 0.2.0 release. I'll try to make a little bit of time to get it out by the end of the week. |
Thanks @orbeckst! Please let me know if there's anything I can do to help; I don't recall if we shared PyPI permissions for publishing packages there. |
Just checked, and currently I'm the sole collaborator on the PyPI package. If you can send me your PyPI username I can add you as an owner as well. |
Done! |
alchemlyb and alchemtest 0.3.0 are released. (Yes, it should have been 0.2.0 but I accidentally labelled alchemtest already as 0.3.0 and then alchemlyb followed suite. There's no deeper reason. With semantic versioning this is not going to be a problem, we just can't backdate anything.) |
Thanks @orbeckst! I think 0.3.0 is totally appropriate. Thanks for pushing it through! |
We reached the "Immediate/Pressing" milestones in our roadmap and have a whole bunch of new features as well as really good testing coverage.
I'd like to release a 0.2.0 once the latest Amber parser changes are in. (If we can get a NAMD parser, too, then that would be a bonus, but I don't know what the time line is for that)
Is there anything else that we need to take care of, @alchemistry/alchemlyb ?
The text was updated successfully, but these errors were encountered: