You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The work to introduce dask to Iris and release the results as Iris v2.0 has become the first significant test of Iris' change management whitepaper. This test of the whitepaper appears to show the whitepaper is being a little too conservative on what we can and can't do at an Iris major version release.
We need to consider updating the change management whitepaper to reflect how we actually need to manage change at Iris major versions. It may be that we need to be less conservative about change at major versions – while, of course, adhering to SemVer.
We added the temporary removal of the whitepaper pending further updates in #2862. I'll therefore move this out of the 2.0.0 milestone, but we certainly need to resolve this long-term.
The work to introduce dask to Iris and release the results as Iris v2.0 has become the first significant test of Iris' change management whitepaper. This test of the whitepaper appears to show the whitepaper is being a little too conservative on what we can and can't do at an Iris major version release.
We need to consider updating the change management whitepaper to reflect how we actually need to manage change at Iris major versions. It may be that we need to be less conservative about change at major versions – while, of course, adhering to SemVer.
Relates to a discussion started in #2681.
The text was updated successfully, but these errors were encountered: