List view
- Due by March 3, 2025•66/74 issues closed
- Due by May 17, 2024•67/67 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.10.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 16, 2023•51/51 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 19, 2023•43/43 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 March 6, 2023•130/130 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.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 17, 2022•37/37 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 20, 2022•40/40 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.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 21, 2022•67/67 issues closedThis milestone is now locked. No more issues should be added.
Due by October 25, 2021•42/42 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 July 5, 2021•19/19 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 15, 2021•15/15 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 19, 2020•6/6 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 22, 2020•44/44 issues closedAdd a set of PRIMAVERA metrics to ESMValTool on time to be able to test them for Milestone 3
No due date•2/6 issues closed