-
Notifications
You must be signed in to change notification settings - Fork 286
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
Release 2.1.0 #3038
Comments
#3045 Fixes the version switcher and updating the README image URL. |
#3044 implements the what's new. |
#3046 updates the cf-standard-names |
#3047 closes the existing release branches |
Handing over some of this to @dkillick, who will have some time to look at it in 12-18 hours as I'm not available for 3 days. |
Docs PRs: SciTools/scitools.org.uk#204 and SciTools/scitools.org.uk#201 |
I've just written down a high-level overview of the release checklist in https://github.com/SciTools/iris/wiki/Release-checklist-guidance. I hope this is useful and not too much detail. I've xrefd this issue so that people can see an example of it used in practice. cc @SciTools/iris-devs |
@pelson Can I suggest an addition to the release checklist:
Met Office Science tweeted about the release of Iris 2.1 on our behalf and have encouraged us to do so again with each release. This seems like the most sensible place to make sure we remember to do that. |
Looks like Iris 2.1.0 has not yet been announced on the users' google group... |
Good point. This is my fault for not specifying the "user's mailing list", @dkillick announced it on the dev mailing list... I've just posted something on the users list now. @kaedonkers - I'm reluctant to make it one of the checklist items, but definitely support improved PR around releases where appropriate. |
Planning to release a v2.1.0 over the next week or so (target 6th June 2018).
Reminders for me:
Ensure a what's new directory exists for v2.2 (and think about whether this process continues to make sense)(note: this doesn't make sense, as you have to have a file in order to add the directory, and there isn't any what's new yet. Personally, I see the what's new stuff flawed. I'll address this over the next few weeks, but not for v2.1)The text was updated successfully, but these errors were encountered: