Hi all, Following the earlier “Planned Feature List for IoTDB 2.0.11” discussion on this mailing list, I would like to ask for community feedback on whether we are ready to move into the stabilization and testing phase.
I propose that we: 1. Freeze the feature scope for IoTDB 2.0.11. 2. Cut the rc/2.0.11 branch from master. 3. Start focused testing and stabilization work for the 2.0.11 release. After the branch is cut, I propose that only fix commits directly related to the 2.0.11 release-note items confirmed through this discussion be merged into rc/2.0.11. New features and unrelated changes would continue on master for a future release. This is a proposal for community discussion, not a finalized decision. Before we cut the branch, please share any concerns, missing must-have release-note items, or in-progress changes that you believe should be considered for 2.0.11. If possible, please include the corresponding GitHub issue or pull request and its current status so that the community can review it together. If the community agrees on the scope and timing, we can then proceed with cutting the branch and coordinate the testing work openly through this mailing list and GitHub. Best regards, Yuan Tian
