Bumps the version for 2.1dev + v2.0x what's new tweaks#2937
Bumps the version for 2.1dev + v2.0x what's new tweaks#2937DPeterK merged 3 commits intoSciTools:masterfrom
Conversation
lib/iris/__init__.py
Outdated
|
|
||
| # Iris revision. | ||
| __version__ = '2.0.0rc1' | ||
| __version__ = '2.1.0dev1' |
There was a problem hiding this comment.
| coordinates to plot as the x and y axis of a plot. | ||
|
|
||
| * The cf_units dependency version has been updated to v1.2.0, which prints shorter | ||
| unit strings. |
There was a problem hiding this comment.
I included a little example with this whatsnew item - did you elect to leave it out?
There was a problem hiding this comment.
Good spot. No it wasn't intentional.
| functionality is now delivered through :mod:`iris-grib`. | ||
|
|
||
| * In Iris v1 it was possible to configure Iris to log at import time through | ||
| :attr:`iris.config.LOGGING`. This capability has been removed in iris v2. |
There was a problem hiding this comment.
Does this attribute actually still exist or will we end up with a broken link in the docs?
There was a problem hiding this comment.
Could you also capitalise the last "iris" to be consistent with the other examples of the word in this point please.
There was a problem hiding this comment.
FWIW the what's new can be read at https://scitools-docs.github.io/iris/v2.0.x/whatsnew/2.0.html (once the cache is updated, it will also be available at http://scitools.org.uk/iris/docs/v2.0/whatsnew/2.0.html)
There was a problem hiding this comment.
OK I've checked the built whatsnew and there isn't a link to LOGGING. It doesn't really impact the page though because the text falls back to preformatted.
| * In Iris v1 it was possible to configure Iris to log at import time through | ||
| :attr:`iris.config.LOGGING`. This capability has been removed in iris v2. | ||
|
|
||
| * When coordinates have no well defined plot axis, iris.plot and iris.quickplot |
There was a problem hiding this comment.
Links to modules?
Also, 'axis' --> 'axes', probably. Update: In fact, I think that either works here. Up to you whether you change it or not.
* v2.0.x: Converted the contributions into the whatsnew.
Here are the doc changes I made directly to the v2.0.x branch. If we want to change them in any way, we would need a PR to the upstream/v2.0.x branch (happy to do that, or the reviewer can do it directly).