Some suggestions about our release schedule - Re: [DISCUSS] ready for release v0.12.3?

[Eric Pai]

Hi,

It's very nice that we have so many incoming fixes, but should we make the 
patch version be released at a fixed schedule, i.e. 2 weeks or 4 weeks, if no 
critical bug is fixed?

I think the benefit is making all the community contributors and new version 
pioneers know when to release next version, and do a better development or 
upgrading plan.

在 2021/9/16 上午11:42，“Jialin Qiao”<qiaojia...@apache.org> 写入:

    Hi,

    So efficient !?

    +1 to release 0.12.3.

    Thanks,
    —————————————————
    Jialin Qiao
    School of Software, Tsinghua University

    乔嘉林
    清华大学 软件学院


    Haonan Hou <hhao...@outlook.com> 于2021年9月16日周四 上午11:32写道：

    > 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