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.

Sign up for GitHub

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

Jump to bottom

Move to new Fortran API #507

Closed
toxa81 opened this issue Jun 23, 2020 · 3 comments
Closed

Move to new Fortran API #507

toxa81 opened this issue Jun 23, 2020 · 3 comments
Assignees
@toxa81

Comments

@toxa81
Copy link
Collaborator

toxa81 commented Jun 23, 2020

@mtaillefumier @simonpintarelli @AdhocMan @haampie

I plan to update the Fortran API. I propose to merge everything which is stable to master branch and tag it. Then I will update the develop branch with the new API and make a new pre-release. At this moment, QE and CP2K need to be adjusted to the new pre-release. Do you seen any obvious problems that I missed?
@toxa81 toxa81 self-assigned this Jun 23, 2020
@haampie
Copy link
Collaborator

haampie commented Jun 23, 2020

Seems fine to me. Is there any advantage of keeping the develop branch around actually?

@toxa81
Copy link
Collaborator Author

toxa81 commented Jun 23, 2020

@haampie Yes, it helps to test new functionality. We had a short discussion here
#464

@mtaillefumier
Copy link
Collaborator

It seems fine to me as well. I will adjust cp2k when the new interface is in develop.

@toxa81 toxa81 closed this as completed Dec 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@toxa81 toxa81

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@haampie @toxa81 @mtaillefumier