I agree with Tian Jiang's opinion.

We may need a branch for the cluster version's experimental features
development, but whether we need a "cluster_release" depends on whether we
release the stand-alone (single node) version and the cluster version
separately.

Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


谭新宇 <[email protected]> 于2020年10月12日周一 下午4:05写道:

> Hi Houliang:
>
> Great suggestion!
>
> Big +1 for checking out a cluster_release branch to merge stable and
> tested features from cluster_new(cluster_develop).
>
> Looking forward to our first cluster release version!
>
> Thanks
> ____________
> Xinyu Tan
>
> > 在 2020年10月12日,下午3:28,Haimei Guo <[email protected]> 写道:
> >
> > Looks good!
> >
> > On Mon, Oct 12, 2020 at 12:23 PM Houliang Qi <[email protected]> wrote:
> >
> >> Hi all,
> >>
> >>
> >> I’d like to start a discussion about the cluster version management:
> >>
> >> As someone mentioned  that there should be a develop branch and a
> release
> >> branch[1]. The develop branch is used to submit the latest development,
> and
> >> the release branch is used for the functions that need to be released in
> >> the latest release.
> >>
> >> At the same time, I hope that the development of cluster can also have
> two
> >> branches: cluster_develop branch and cluster_release branch.
> >>
> >> The cluster_develop branch is used to merge the stand-alone version of
> the
> >> develop branch code and the latest development of the cluster.
> >>
> >> The cluster_release branch is used to release some of the latest
> features.
> >> Only the functions that need to be released are allowed to be merged
> into
> >> the cluster_release branch, or to fix some bugs. Other newly developed
> >> functions are not allowed to be merged into the cluster_release branch.
> >> After cluster_release has been fully tested, it can be released.
> >>
> >> Regarding the latest release, I would like to check out a
> cluster_release
> >> branch after the cluster_premerge branch merges into the master
> (develop),
> >> and then the master branch merges into the cluster_new (cluster_develop)
> >> branch.
> >>
> >> And I think the new functions do not have beed tested or need more than
> >> one month to tested should be switch off when release the cluster
> version.
> >>
> >> Does anyone have some ideas about this?
> >>
> >>
> >> [1]
> >>
> https://lists.apache.org/thread.html/rf7dce8d4cfcf4001feeba139cc897d6b40a1741e06ef87aabd56d8c9%40%3Cdev.iotdb.apache.org%3E
> >>
> >>
> >>
> >>
> >> Thanks,
> >> ---------------------------------------
> >> Houliang Qi
> >>
> >>
> >
>
>

Reply via email to