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

PSyclone release 2.4.0 #2108

Closed
12 tasks done
TeranIvy opened this issue Apr 17, 2023 · 14 comments
Closed
12 tasks done

PSyclone release 2.4.0 #2108

TeranIvy opened this issue Apr 17, 2023 · 14 comments
Assignees
Labels
in progress Release Planning and creating PSyclone releases

Comments

@TeranIvy
Copy link
Collaborator

TeranIvy commented Apr 17, 2023

The related fparser 0.1.2 release issue is stfc/fparser#419.

Update 1: going with fparser 0.1.1 (see comment below).

Update 2: going with fparser 0.1.2 (see comment below).

Update 3: going with fparser 0.1.3 (see comment below).

Update 4: Terry reported an issue with PSyAD following the recent merge of #2233. Added the follow-up issue, #2335.

Update 5: we agreed that #2335 is not a priority for this release so I removed it. I will do one final testing of LFRic before I conclude the task list as completed.

Required PSyclone issues/PRs to be completed (20/09/2023):

Update on the related PSyclone PRs/issues;

@TeranIvy TeranIvy added the Release Planning and creating PSyclone releases label Apr 17, 2023
@TeranIvy
Copy link
Collaborator Author

Update: fparser did not support module procedure :: (F2008 standard) so that was fixed in stfc/fparser#406 (associated issue stfc/fparser#405)

@TeranIvy
Copy link
Collaborator Author

Update: fparser was throwing a syntax error when parsing source which INCLUDEs an INTERFACE block. That was fixed in stfc/fparser#414.

arporter added a commit that referenced this issue Jun 19, 2023
@arporter
Copy link
Member

Created branch 2108_release240 and updated fparser on this branch to permit testing by @TeranIvy or @mo-lottieturner :-)

@TeranIvy
Copy link
Collaborator Author

@arporter, I am happy to report that everything is fine with the new fparser 😃

@arporter
Copy link
Member

@TeranIvy and @mo-lottieturner, I've just brought the branch associated with this Issue up-to-date with master.
How do you want to proceed with making a release?

@arporter
Copy link
Member

@sergisiso has suggested getting #2218 on as well as that has some LFRic fixes.

@arporter
Copy link
Member

#2218 is on master now.

@arporter
Copy link
Member

I've updated the associated branch although you could just test with master. I'll let @TeranIvy, @mo-lottieturner, @sergisiso and @rupertford take it from here...

@TeranIvy
Copy link
Collaborator Author

TeranIvy commented Sep 15, 2023

PSyclone setup.py still requires fparser 0.1.1, and when installing PSyclone from the master or a branch it pulls in both fparser 0.1.1 release and 0.1.2 submodule. I will issue a PR for this as it is complicating testing on our end.

Update: We decided to go with fparser 0.1.3 (stfc/fparser#427).

@arporter
Copy link
Member

We need to fix ReadTheDocs builds #2242 before making a release too.

@TeranIvy
Copy link
Collaborator Author

TeranIvy commented Sep 20, 2023

@rupertford, @arporter, @sergisiso and @hiker, I updated the issue with required tasks/PRs. Please check whether I forgot something 😄

@TeranIvy
Copy link
Collaborator Author

LFRic test suite on Spice ran successfully with the latest PSyclone master.

arporter added a commit that referenced this issue Sep 29, 2023
arporter added a commit that referenced this issue Sep 29, 2023
@arporter
Copy link
Member

I've updated the version number and rebuilt the UG. Just waiting for the integration tests now.

@arporter
Copy link
Member

Integration tests are all fine. Will proceed to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in progress Release Planning and creating PSyclone releases
Projects
None yet
Development

No branches or pull requests

5 participants