Hi all, We would like to skip the IoTDB 2.0.9 release and proceed directly with the 2.0.10 release.
The main reason is that one release-note item originally planned for 2.0.9 remained under active development and iteration longer than expected. By the time this item was fully completed, the development work planned for 2.0.10 had also been finished. Given this situation, releasing 2.0.9 separately would bring limited practical value and may instead cause unnecessary confusion. Therefore, we plan to include the relevant changes in 2.0.10 and make 2.0.10 the next release version. To make future release planning clearer, starting from 2.0.11, before each release iteration begins, we will send an email to the mailing list outlining the release-note items expected to be included in that version, together with the expected code-freeze date. Everyone is also welcome to propose additional release-note items that should be included in the corresponding version. Please note that the code-freeze date is not the same as the release date. After code freeze, we will still need to test and verify the corresponding release-note items before proceeding with the formal release. Please let us know if you have any concerns or objections. Best regards, ------------------------ Yuan Tian
