Wow, it will be a big event in IoTDB history. We have waited for the moment in 
almost 1 year :)

BTW, 
1. what's the time plan of the code frozen of v1.0.0? We should let all the 
contributors know the close time of new features accepted window.
2. And are there any APIs, including SQL, Session SDK, REST etc, needed to do 
break changes? 
In my view, we had often made in incompatible changes when v0.x versions were 
released.
After we release v1.0.0, we should obey the semantic version that no break 
changes are made before v2.0.0 released, or we need define an API deprecation 
procedure.
We should let user migrate the API calls smoothly after upgrading from v1.0.0 
to other new versions of v1.x.

在 2022/10/11 14:36,“Jialin Qiao”<[email protected]> 写入:

    Hi all,

    After nearly 4 years since we join the ASF in 2018 and one year
    development of the Cluster version, we released several versions, from
    0.8 to 0.14.

    Now, we prepare to release a formal cluster version in the end of next
    month, and I propose that we call this version 1.0.0.

    Thank all for contributing to the cluster version, what do you think?

    Thanks,
    —————————————————
    Jialin Qiao
    Apache IoTDB PMC

Reply via email to