-
Notifications
You must be signed in to change notification settings - Fork 1
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
Set up issue tracking for CISM and CISM-wrapper development towards NorESM3 #4
Comments
Hi Michele, hi Steve, I have started to set up issue tracking for CISM and CISM coupling towards NorESM3. I have located the issues with NorESMhub/CISM-wrapper, thinking that focus is now on the coupling and that CISM bugs would likely enter at ESCOMP/CISM instead. Thanks, Heiko |
@hgoelzer, this new tab in the NorESM Development project looks good to me. It will track any open issue or PR from CISM-wrapper. If you are interested in also tracking select issues in ESCOMP/CISM, have a peek at View 22 which I set up as a test. Here, you can manually add any open issue or PR from ESCOMP/CISM. |
@gold2718, nice. Thanks for checking. |
Oops, I forgot to add that. What I did is click the "+ Add item" link at the bottom of the "Todo" column and type in Should I add the change to the CISM tab (and remove View 22)? |
The change is to add "ESCOMP/CISM" as a source repo for this view. This does not automatically add everything from ESCOMP/CISM because those issues and PRs are not in the NorESMhub Development project. Note that this change does not affect the view of the issue or PR from https://github.com/ESCOMP/CISM because the project belongs to a different organization. |
OK, I see. So that was a manual add. I assume the same approach would work to add CISM issues to the NorESM2.5 view. Thanks for the details. Yes, you can add the changes to the CISM tab and remove View 22. Thanks |
Purpose:
Get CISM development into the general NorESM dev workflow. Make it convenient to insert, track and process issues, bugs and TODOs
Description:
This is the first issue to test the process
Extra details:
The text was updated successfully, but these errors were encountered: