-
Notifications
You must be signed in to change notification settings - Fork 32
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
Make a release compatible with aiida-core~=2.0
#300
Comments
@yakutovicha @adegomme Could you please make a release to PyPI of the tag that is compatible with @pzarabadip @espenfl Is there still work required before a release can be made of the current @janssenhenning @broeder-j What is the current status or plans to upgrading the @sponce24 Creating a 2.0-compatible release for |
Hi @sphuber. I just released a new version of |
For the information: the |
@sphuber aiida-fleur now has a PyPi release with support of AiiDA 2.X |
@sphuber, I believe all the plugins now migrated to 2.0.0. Correct? |
Bigdft definitely doesn't, and according to the table neither do abinit and wien2k. Although those may have had a release. I have done work on both to get them to V2 compatible release, but I don't remember if I managed to finish. I'm on holiday now so can't check in detail, but can look next week. Anyway, bigdft will take more work because @ljbeal started a complete rewrite and it is not clear how far away from release that is |
@sphuber I see that the 10 of January aiida-bigdft v0.3.0 has been released with compatibility for aiida 2.0 (@ljbeal can confirm). Same goes for aiida-wien2k and aiida-abint (for both you did the release) . Also on pyPI everything is available. That's the reason why I'm asking. I believe we are ready to go. |
Seems you're right. I spoke to @ljbeal on January 5th and he told me he was busy with a complete rewrite/refactor on his personal fork https://github.com/ljbeal/aiida-bigdft/ which is why there hadn't been a new release yet. The idea was to release this at some point but it wasn't ready. I lost track of this due to other commitments, but also hadn't heard anything since, which is why I was under the impression the migration wasn't completed yet. I am a bit confused what the situation now is, because the original repo now points the to Louis' fork as the source: Anyway, I have updated this branch to point to the new version and if the tests pass, I think we are good to go. Edit: tests fail. Apparently the new version of |
Disclaimer: This does not affect the work on the current paper which will be finalized using
aiida-core~=1.6
. This is just an issue to start monitoring the progress towards a v2.0-compatible release in the future.aiida-abinit
v0.5.0
aiida-bigdft
v0.3.0
aiida-castep
v2.0.0
aiida-cp2k
v2.0.0
aiida-fleur
v2.0.0
aiida-gaussian
v2.0.0
aiida-nwchem
v3.0.0
aiida-orca
v0.6.0
aiida-quantumespresso
v4.0.0
aiida-siesta
v2.0.0
aiida-vasp
v3.0.0
aiida-wien2k
v0.2.0
The text was updated successfully, but these errors were encountered: