Closed ligiabernardet closed 4 years ago
@jedwards4b
@ligiabernardet Thanks!
@ligiabernardet there is also the update that needs to come to chgres_cube to change from using nemsio files to nc files. These files will replace the nemsio files when gfsv16 goes into operations. Because of the amount of testing involved I want to be careful about the number of upgrades we do
I agree that we need to be careful about the number of upgrades we do because of limited staffing. Mostly we need to create a plan. If we have agreement that the innovations for 1.1 should go to existing public release branches, that is a good start. We can issue this issue to collect a list of the desired upgrades. Updated list below.
Updated list by request from @climbfuji.
@climbfuji You mentioned we should consider an upgrade to the build system. Would you be able to explain what that entails, and which code repositories that would affect?
It would be helpful to also describe how these upgrades would interact with the CIME build system in the release.
On Mon, Apr 20, 2020 at 11:43 AM ligiabernardet notifications@github.com wrote:
@climbfuji https://github.com/climbfuji You mentioned we should consider an upgrade to the build system. Would you be able to explain what that entails, and which code repositories that would affect?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ufs-community/ufs-mrweather-app/issues/149#issuecomment-616708915, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4XCEYOYW45LRTY6UZVOYLRNSCS3ANCNFSM4LUJLWYQ .
-- Mariana Vertenstein CESM Software Engineering Group Head National Center for Atmospheric Research Boulder, Colorado Office 303-497-1349 Email: mvertens@ucar.edu
Updated list of potential updates
Add metadata to chgres output https://github.com/NOAA-EMC/UFS_UTILS/issues/97
UPP had bug fix merged into branch v1.0, details here in EMC_post Issue 129 . Should confirm this was tested and/or test again. @aerorahul contributed this bug fix.
Also: need update for jet (filesystem changes)
I started collecting changes to the ufs-weather-model and submodules, see https://github.com/ufs-community/ufs-weather-model/pull/149 and associated PRs (currently in draft status).
Is there a time line for when component repos (e.g. UPP) should be creating v1.1 branch (from public-v1 branch as discussed)? Should this be created now so testing can use that v1.1 branch and any necessary fixes go into that new branch? Or wait until closer to release, and while waiting any new features/fixes go into branch public-v1?
Is there a time line for when component repos (e.g. UPP) should be creating v1.1 branch (from public-v1 branch as discussed)? Should this be created now so testing can use that v1.1 branch and any necessary fixes go into that new branch? Or wait until closer to release, and while waiting any new features/fixes go into branch public-v1?
Bad time to ask this question. I wasted hours today figuring this out. See https://github.com/ufs-community/ufs-weather-model/pull/149.
@climbfuji Yikes! Ok, I'll wait until this is hashed out. No rush on UPP side, just wanted to stay informed of process.
I am closing this issue since the specific work needed for the 1.1.0 release has been distributed through various issues.
We need to create a plan for upcoming releases of the MR W App, both for fixes 1.0.x and for upgrades, 1.x. @arunchawla-NOAA @mvertens @lbnance @junwang-noaa @ceceliadid
Must decide which branches will be used for the release (some offline emails indicate it will be the same release branches already used for the 1.0.0 release because the main development branches have too many new capabilities).
For upcoming releases, @llpcarson and I would like to point most of the documentation URLs to the head of release branch (not the tag). This will facilitate adding bug fixes and clarifications to the documentation as we get feedback from the community.
So far I have identified the following list of potential upgrades to be included: