<div dir="ltr">Hi all,<div><br></div><div>I have been asked whether NEMS development is frozen because some people are already working from git. Only the NEMS framework trunk and "NEMS" project vlab git master are frozen. Please work in Subversion if you can. However, wherever you need to do your NEMS development, please continue to do so. I cannot even guess what the resolution of this problem will be, but we cannot afford to freeze development of the NEMS. Just keep in mind that the subversion trunk and git master are frozen until we find an acceptable solution, so your developments will not end up in the trunk or master for a little while. Once we figure out where and how NEMS framework development will happen, we'll move development over to that location as painlessly as possible.</div><div><br></div><div>As a reminder, these two directories are frozen:</div><div><br></div><div><div>EMC Subversion: <a href="https://svnemc.ncep.noaa.gov/projects/nems/trunk">https://svnemc.ncep.noaa.gov/projects/nems/trunk</a></div><div>VLAB git: ssh://<a href="http://samuel.trahan@vlab.ncep.noaa.gov:29418/NEMS">samuel.trahan@vlab.ncep.noaa.gov:29418/NEMS</a></div></div><div><br></div><div>In VLAB git, the master is frozen and any commits submitted via gerrit code review will be rejected.</div><div><br></div><div>Sincerely,</div><div>Sam Trahan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 31, 2017 at 6:13 PM, Samuel Trahan - NOAA Affiliate <span dir="ltr"><<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>Due to a repository issue, the NEMS trunk is temporarily frozen.</div><div><br></div><div>At present, there are two, distinct, NEMS framework repositories:</div><div><br></div><div>EMC Subversion: <a href="https://svnemc.ncep.noaa.gov/projects/nems/trunk" target="_blank">https://svnemc.ncep.noaa.gov/<wbr>projects/nems/trunk</a><br></div><div>VLAB git: ssh://<a href="http://samuel.trahan@vlab.ncep.noaa.gov:29418/NEMS" target="_blank">samuel.trahan@vlab.ncep.<wbr>noaa.gov:29418/NEMS</a><br></div><div><br></div><div>Those are the ONLY directories that are frozen. Anything else in NEMS can develop as usual.</div><div><br></div><div>The second one is not live; nobody should be using it. The NEMSfv3gfs app points to the second one while all other apps point to the first. There is no automatic sync between the two, and our commit process has not been updated to deal with two, distinct, repositories. This is contrary to NEMS git transition plan, and creates a situation where commits are dangerous.</div><div><br></div><div>Until this issue is resolved, in my capacity as the NEMS code manager, I am freezing the NEMS trunk and NEMS git master. There will be no trunk or master commits except for emergencies.</div><div><br></div><div>Sincerely,</div><div>Sam Trahan</div></div>
</blockquote></div><br></div>