List view
Please add this milestone to any issue or pull request you are planning to work on and would like to have included in the v2.13.0 release. Note that it is your own responsibility to make sure that the work is merged into the main branch by the due date. Anything that is not ready in time, can be included in the next release.
Due by August 18, 2025•46/46 issues closed- Due by November 29, 2024•3/3 issues closed
Please add this milestone to any issue or pull request you are planning to work on and would like to have included in the [v2.12.0 release](https://docs.esmvaltool.org/en/latest/community/release_strategy/release_strategy.html#release-schedule). Note that it is your own responsibility to make sure that the work is merged into the main branch by the due date. Anything that is not ready in time, can be included in the next release.
Due by February 11, 2025•96/96 issues closedPlease add this milestone to any issue or pull request you are planning to work on and would like to have included in the [v2.11.0 release](https://docs.esmvaltool.org/en/latest/community/release_strategy/release_strategy.html#release-schedule). Note that it is your own responsibility to make sure that the work is merged into the `main` branch by the due date. Anything that is not ready in time, can be included in the next release.
Due by May 3, 2024•95/95 issues closedPlease add this milestone to any issue or pull request you are planning to work on and would like to have included in the [v2.10.0 release](https://docs.esmvaltool.org/en/latest/community/release_strategy.html#release-schedule). Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by October 2, 2023•53/53 issues closedPlease add this milestone to any issue or pull request you are planning to work on and would like to have included in the v2.9.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by June 5, 2023•66/66 issues closedPlease add this milestone to any issue or pull request you are planning to work on and would like to have included in the v2.8.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by February 20, 2023•86/86 issues closed- No due date•2/2 issues closed
Please add this milestone to any issue or pull request you are planning to work on and would like to have included in the v2.7.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by October 3, 2022•24/24 issues closedPlease add this milestone to any issue or pull request you are planning to work on and would like to have included in the v2.6.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by June 21, 2022•56/56 issues closedThis is a milestone for a potential bugfix release. Right now there are no plans to do such a release, but if issues accumulate here or if it becomes urgent, we'll take it into consideration.
No due datePlease add this milestone to any issue or pull request you are planning to work on and would like to have included in the v2.5.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by February 7, 2022•95/95 issues closedThis is a milestone for a tentative bugfix release. Here, we can collect issues/PRs that might make a bugfix release necessary. If this stays empty, or we decide the severity of the accumulated issues doesn't warrant a bugfix release, we'll leave it at that.
No due date•17/17 issues closedPlease add this milestone to any issue you are planning to work on and would like to have included in the v2.4.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by October 4, 2021•53/53 issues closedThis milestone is now locked; no new features can be added. It will be used to track open and newly discovered bugs until the release.
Due by June 14, 2021•37/37 issues closedPlease add this milestone to any issue you are planning to work on and would like to have included in the v2.2.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by February 1, 2021•18/18 issues closedPlease add this milestone to any issue you are planning to work on and would like to have included in the v2.1.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by October 5, 2020•5/5 issues closedPlease add this milestone to any issue you are planning to work on and would like to have included in the v2.0.0 release. Note that it is your own responsibility to make sure that the work is done by the due date. Anything that is not done in time, can be included in the next release.
Due by July 1, 2020•15/15 issues closedChanges in ESMValCore necessary for IPCC AR6 recipes/diagnostics.
No due date•9/9 issues closedChanges in ESMValCore necessary for recipes/diagnostics in ESMValTool papers.
Due by March 13, 2020•10/10 issues closed