[Ncep.list.nems.announce] trying to understand a recent NEMS commit...
Nicole McKee - NOAA Affiliate
nicole.mckee at noaa.gov
Fri Feb 28 12:30:36 UTC 2014
I can really only respond to your number 1. Others had issues with not
getting the announcement email about the 6.3.0r update also. It turns out
that it was announced using the NEMS Trac tickets listserv instead of the
nems.announce list. I'll double check to see if you were subscribed to the
Trac ticket listserv. Then you will also get emails whenever a NEMS ticket
is created or updated. But, the nems.announce list was created for the sole
purpose of ensuring all NEMS developers receive commit updates.
We should make a point to be consistent in our announcements, using the
same email list, creating/updating our tickets, etc.
IMSG/NCEP-EMC Global Modeling Branch
On Thu, Feb 27, 2014 at 7:47 PM, Gerhard Theurich <theurich at sourcespring.net
> I am a bit puzzled how I missed the commit announcement to the NEMS
> trunk that went in 19h ago as revision 37397. There are two issues:
> 1) It's hard to merge to the trunk when there are changes coming like
> that are not being announced. Yesterday I had merged branches/NUOPC
> changes to a trunk sandbox, resolved issues and started testing. I will
> repeat now...
> 2) The changes in question, updating to ESMF v6.3.0r in NEMS, I would
> have advised to approach the issue differently. Starting with v5.2.0r,
> ESMF guarantees a large degree of backward compatibility of the API. The
> idea behind added the "520rAPI" setting in NEMS was to use it on all
> 520rAPI compatible ESMF releases, which should be pretty much any future
> release. The same internal macros would be used in NEMS, and eventually,
> when the use of prior ESMF versions (like v3.1.0rpX) dies out in NEMS,
> all of that ESMF version specific macro jungle could be cut down. I
> think we should revisit the changes.
> Ncep.list.nems.announce mailing list
> Ncep.list.nems.announce at lstsrv.ncep.noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ncep.list.nems.announce