Hi,
The v0.12.2 was just released 3 days ago, and before that, we draft a release every 2 or 3 months. Thus I believe we shouldn't break the convention unless it is necessary to release a hotfix version that carries fixes to critical issues. In my opinion, the fixes since v0.12.2 are not critical enough for a hotfix version. Maybe it is better to release v0.12.3 later. Thanks, Zhong 原始邮件 发件人:"Haonan Hou"< hhao...@outlook.com >; 发件时间:2021/9/16 11:32 收件人:"dev-iotdb"< dev@iotdb.apache.org >; 主题:[DISCUSS] ready for release v0.12.3? Hi all, I see some bug-fix PRs for rel/0.12 branch are merged after 0.12.2 released. * [IOTDB-1275] Fix backgroup exec for cli -e function causes an infinite loop * [IOTDB-1287] Fix C++ class Session has 2 useless sort() * [IOTDB-1289] fix CPP mem-leak in SessionExample.cpp insertRecords() * [IOTDB-1619] Fix an error msg when restart iotdb-cluster * [IOTDB-1629] fix the NPE when using value fill in cluster mode * [IOTDB-1632] Fix Value fill function fills even when the data exists * [IOTDB-1659] Fix Windows CLI cannot set maxPRC less than or equal to 0 * [IOTDB-1670] Fix cli -e mode didn't fetch timestamp_precision from server * [IOTDB-1674] Fix command interpret error causing somaxconn warning failed * [IOTDB-1677] Fix not generate file apache-iotdb-0.x.x-client-cpp-linux-x86_64-bin.zip.sha512 * [IOTDB-1678] Fix client-cpp session bug: can cause connection leak. * [IOTDB-1679] client-cpp: Session descontruction need release server resource * [ISSUE-3945] Fix Fuzzy query not support multiDevices and alignByDevice Dataset * fix IoTDB restart does not truncate broken ChunkGroup bug * fix merge ClassCastException: MeasurementMNode * change sync version check to major version So, Is it time to release v0.12.3? Best, Haonan Hou