In the meeting with ShardingSphere PMC zhangliang，
He said that multiple release manager to handle release will be helpful for the
community.
Before, we follow the same release process as below.
1. jiashun add a tag and build a tarball.
2. I collect important bugfixes and big features integrated (if exists) as
release note
3. I will call for vote in our dev mail list and incubator list.
Gaidong, how about your guys to participate in the release work?
Release is very important for every open source project.
Thanks.
在 2020/5/29 下午4:50，“牟盖东”<mougaid...@gmail.com> 写入:
OK, I agree that we keep a stabe release schedule.
tan zhongyi <zhongyi....@gmail.com> 于2020年5月29日周五 上午10:11写道：
> Hi, gaidong,
>
> We don’t need to integrate big feature in every release.
> I just want to make our release schedule more stable or more regular,
> As long as there are fixes, we can make a release every quarter.
>
> How about it?
>
>
>
>
> 在 2020/5/29 上午8:48，“牟盖东”<mougaid...@gmail.com> 写入:
>
> It's good, but can we introduce enough new features to produce an
> acceptable changing list in every release cycle if there is no bug
fix?
> Does that matter?
>
> JiashunZhu <zhujiashun2...@gmail.com> 于2020年5月28日周四 上午10:58写道：
>
> > Yeah it's a good idea. If things go well, maybe we can release our
> first
> > 1.0.0 version by the end of this year.
> >
> > tan zhongyi <zhongyi....@gmail.com> 于2020年5月25日周一 下午1:45写道：
> >
> > > Hi, guys,
> > >
> > > How do you feel this proposal?
> > >
> > > One version for a quarter.
> > > We can build a tag/make a vote internal/ then external on the
> begin of
> > > June.
> > >
> > > Of course, if there is a high priority bugfix such as security
fix,
> > > We can make a release after it.
> > >
> > > Thanks
> > >
> > >
> > >
> > >
> >
> > --
> > Jiashun Zhu
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
> For additional commands, e-mail: dev-h...@brpc.apache.org
>
