Hi all, The discussion on freezing the feature scope for IoTDB 2.0.11 has been open for more than 72 hours, and no concerns, objections, or additional must-have items have been raised.
Based on this lazy consensus, the feature scope for IoTDB 2.0.11 is now frozen. I have created the rc/2.0.11 branch from master at commit 2c77de36: https://github.com/apache/iotdb/tree/rc/2.0.11 We are now entering focused testing and stabilization for the 2.0.11 release. >From this point forward: - Only fixes directly related to the confirmed 2.0.11 release-note items, including issues found while testing those items, should be merged into rc/ 2.0.11. - New features and unrelated changes should continue on master. - Any proposed exception should first be raised on the dev list, together with the corresponding GitHub issue or pull request, for community discussion. Please report testing findings through GitHub issues and share the relevant issue or pull request on this list when coordination or discussion is needed. Thank you to everyone who contributed to the scope discussion. Help with testing and stabilization is very welcome. Best regards, Yuan Tian On Wed, Jul 15, 2026 at 7:51 PM Yuan Tian <[email protected]> wrote: > 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 >
