-
Notifications
You must be signed in to change notification settings - Fork 100
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
Updates in branch develop #166
Comments
Commit 4b531bc : #167 Update CMakeModules submodule from @DusanJovic-NOAA |
Commit 36a3366b : #172 Add the changes in the read interface INIPOST.F for 3drma for assigning 10m u/v for 3drtma. |
Commit 4ef55cd: sync # 151, 163, 176, 178, 183, 185, 187, 190, 192, 199 from branch release/gfs_v16. |
Commit 2043340 : #233 : Update with fortran 90 syntax, e.g. relational operator and none explicit statement. |
Commit 194da1 : #244 : Replace random_nember call from fortran standard subroutine instead of mersenna twiester at w3emc. A new tag upp_v10.0.1 was created for installing upp/10.0.1 at hpc-stack. |
Commit 638479 : #255 : support regional in-line post at ufs-weather-model. |
@WenMeng-NOAA what I would like to suggest is that you handle these updates like other NCEP software packages. Instead of adding these notes to this long-running issue, you update the Release Notes for the next release. Then, when the release happens, all these notes are easily available to the user. For example, see these release notes: |
@edwardhartnett Good suggestions. This issue is used for my own reference of updates in develop branch. |
This information (what has been updated in each relaese) is not just of interest to you - it is also interesting to users. By keeping these notes in the release notes, as we do in other NCEP projects, you can keep them for yourself, but they would also be helpful to the users. |
@edwardhartnett - Yes agreed, this is incredibly helpful for users. @WenMeng-NOAA - I can look at starting this in conjunction with upcoming UFS app releases. |
What works well is to create a draft release, and then fill it in as you go. Then, when the release is accomplished, the documentation is all there. I will create a draft release and you can see what I mean... OK, I have created a draft new release. However, I'm not sure what version number to use - what will the next release version be? Just be carefull when editing the release notes to hit "Save as Draft" rather than "Publish Release". You only what to hit "Publish Release" when everything is complete and the release is ready to go. |
@edwardhartnett - Thanks, yes I'm familiar with draft releases and set them up for public releases. I also use the method you're describing for another project, I think it will work well. |
The develop is the main development branch. Since 08/17/2020, all updates in develop will be documented in this issue.
The text was updated successfully, but these errors were encountered: