-
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
Stable version numbering (ie 1.x.x) #230
Comments
I agree we're just about there, but I think there are a few things we need to get lined up before pulling that trigger. In particular:
|
I agree. Let's do that and we can make a stable release. |
I've edited the features list to add a two parter for Take2 - I'm going to leave #153 open until we've got an E2E build test on a catalog subset. |
@rbeucher @marc-white Did we decide last week to leave #188 out of this release? |
Yes, pb for later :-) |
We've ticked these all off, so unless there are any more issues that we think are crucial to get fixed, I think we can get ready for a release chaps @rbeucher @marc-white. |
We have a new request on the Hive: @AndyHoggANU also asked me yesterday during TL how much effort this would involve. Currently, they are still deciding where to store the data. My suggestion is that we proceed with a release as planned and then start incorporating the Intake-ESM data stores from NCI. Once the location of the ROMS data is confirmed, we can explore adding it to the catalog. |
One thing that would be good to have is an updated version of the instructions on requesting data to be added to the catalog. |
Pretty sure that's already been done? I just built the documentation from |
We need to ensure that any references to or dependencies on hh5 are removed. With CLEX shutting down, hh5 will no longer be updated after December. Could you please verify that the documentation does not mention hh5? |
@rbeucher this is now being blocked by #273 , which is in turn being blocked by ACCESS-NRI/MED-condaenv#123. |
Considering we are taking over analysis3. |
I tried to load up analysis3 via xp65 in an ARE session, but there seems to be an issue:
|
That was my setup as well, still getting the same issue. Will come back to it again tomorrow. |
OK that environment is now suddenly working for me this morning, must have been a ghost in the machine. Cracking on with updating the notebooks... |
OK I am looking into it |
Hi @marc-white, @charles-turner-1, I’ve successfully updated and fixed the conda environment. The new environment is named Key differences from the current
|
I think we're probably at a point where we don't want to be altering the behaviour of the catalog in a way that will confuse users and/or change workflows substantially.
To reflect this, should we consider updating our version number to a 1.x.x release to indicate that the library interface should be stable?
The text was updated successfully, but these errors were encountered: