You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brpc.apache.org by tan zhongyi <zh...@gmail.com> on 2020/05/25 05:45:20 UTC
How about we make our release more regularly? For example, one
version for one quarter
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
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by JiashunZhu <zh...@gmail.com>.
Hi, Helei & Gaidong,
I have put the document containing detail steps in the attachment. Just
follow the instructions step by step.
Feel free to reach out if you have any questions in the process.
Tan,Zhongyi <ta...@baidu.com> 于2020年6月4日周四 下午5:41写道：
> Cool.
> @JiashunZhu, please tell helei how to do it.
>
> Thanks
>
>
> 在 2020/6/3 下午6:21，“牟盖东”<mo...@gmail.com> 写入:
>
> OK, we take the task 1.
>
> tan zhongyi <zh...@gmail.com> 于2020年6月1日周一 上午11:14写道：
>
> > 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，“牟盖东”<mo...@gmail.com> 写入:
> >
> > OK, I agree that we keep a stabe release schedule.
> >
> > tan zhongyi <zh...@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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org
> > > For additional commands, e-mail: dev-help@brpc.apache.org
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
> For additional commands, e-mail: dev-help@brpc.apache.org
>
--
Jiashun Zhu
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by tan zhongyi <zh...@gmail.com>.
Hi, helei,
Have you add the tag and build the tarball?
If you meet any problem, please refer jiashun,
Thanks.
发件人: JiashunZhu <zh...@gmail.com>
答复: "dev@brpc.apache.org" <de...@brpc.apache.org>
日期: 2020年6月8日 星期一 下午5:54
收件人: "dev@brpc.apache.org" <de...@brpc.apache.org>
主题: Re: How about we make our release more regularly? For example, one version for one quarter
Hi,
I have tried to download the file and it seems ok. Anyway, I attached the file again so that you can check it.
lhestz <lh...@163.com>> 于2020年6月8日周一 下午3:20写道：
The attachment seems to be empty，did you add a wrong file？
错误!未指定文件名。
[图像已被发件人删除。]
lhestz
lhestz@163.com
签名由 网易邮箱大师<https://mailshield.baidu.com/check?q=jldnsK9FTpakcrUkJHvZf40AZ4edgoW73CCxd5E6%2fOCfOAv9AV9OGh7zCD3LijJ8ez5MRAKz4Ko%3d> 定制
On 6/4/2020 17:40，Tan,Zhongyi<ta...@baidu.com> wrote：
Cool.
@JiashunZhu, please tell helei how to do it.
Thanks
在 2020/6/3 下午6:21，“牟盖东”<mo...@gmail.com>> 写入:
OK, we take the task 1.
tan zhongyi <zh...@gmail.com>> 于2020年6月1日周一 上午11:14写道：
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，“牟盖东”<mo...@gmail.com>> 写入:
OK, I agree that we keep a stabe release schedule.
tan zhongyi <zh...@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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org<ma...@brpc.apache.org>
For additional commands, e-mail: dev-help@brpc.apache.org<ma...@brpc.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org<ma...@brpc.apache.org>
For additional commands, e-mail: dev-help@brpc.apache.org<ma...@brpc.apache.org>
--
Jiashun Zhu
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by JiashunZhu <zh...@gmail.com>.
Hi,
I have tried to download the file and it seems ok. Anyway, I attached the
file again so that you can check it.
lhestz <lh...@163.com> 于2020年6月8日周一 下午3:20写道：
> The attachment seems to be empty，did you add a wrong file？
>
> lhestz
> lhestz@163.com
>
> <https://maas.mail.163.com/dashi-web-extend/html/proSignature.html?ftlId=1&name=lhestz&uid=lhestz%40163.com&iconUrl=https%3A%2F%2Fmail-online.nosdn.127.net%2Fqiyelogo%2FdefaultAvatar.png&items=%5B%22lhestz%40163.com%22%5D>
> 签名由 网易邮箱大师 <https://mail.163.com/dashi/dlpro.html?from=mail81> 定制
> On 6/4/2020 17:40，Tan,Zhongyi<ta...@baidu.com> <ta...@baidu.com>
> wrote：
>
> Cool.
> @JiashunZhu, please tell helei how to do it.
>
> Thanks
>
>
> 在 2020/6/3 下午6:21，“牟盖东”<mo...@gmail.com> 写入:
>
> OK, we take the task 1.
>
> tan zhongyi <zh...@gmail.com> 于2020年6月1日周一 上午11:14写道：
>
> 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，“牟盖东”<mo...@gmail.com> 写入:
>
> OK, I agree that we keep a stabe release schedule.
>
> tan zhongyi <zh...@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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org
> For additional commands, e-mail: dev-help@brpc.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
> For additional commands, e-mail: dev-help@brpc.apache.org
>
>
--
Jiashun Zhu
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by lhestz <lh...@163.com>.
The attachment seems to be empty，did you add a wrong file？
| |
lhestz
|
|
lhestz@163.com
|
签名由网易邮箱大师定制
On 6/4/2020 17:40，Tan,Zhongyi<ta...@baidu.com> wrote：
Cool.
@JiashunZhu, please tell helei how to do it.
Thanks
在 2020/6/3 下午6:21，“牟盖东”<mo...@gmail.com> 写入:
OK, we take the task 1.
tan zhongyi <zh...@gmail.com> 于2020年6月1日周一 上午11:14写道：
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，“牟盖东”<mo...@gmail.com> 写入:
OK, I agree that we keep a stabe release schedule.
tan zhongyi <zh...@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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by "Tan,Zhongyi" <ta...@baidu.com>.
Cool.
@JiashunZhu, please tell helei how to do it.
Thanks
在 2020/6/3 下午6:21，“牟盖东”<mo...@gmail.com> 写入:
OK, we take the task 1.
tan zhongyi <zh...@gmail.com> 于2020年6月1日周一 上午11:14写道：
> 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，“牟盖东”<mo...@gmail.com> 写入:
>
> OK, I agree that we keep a stabe release schedule.
>
> tan zhongyi <zh...@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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org
> > For additional commands, e-mail: dev-help@brpc.apache.org
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by 牟盖东 <mo...@gmail.com>.
OK, we take the task 1.
tan zhongyi <zh...@gmail.com> 于2020年6月1日周一 上午11:14写道：
> 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，“牟盖东”<mo...@gmail.com> 写入:
>
> OK, I agree that we keep a stabe release schedule.
>
> tan zhongyi <zh...@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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org
> > For additional commands, e-mail: dev-help@brpc.apache.org
> >
>
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by tan zhongyi <zh...@gmail.com>.
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，“牟盖东”<mo...@gmail.com> 写入:
OK, I agree that we keep a stabe release schedule.
tan zhongyi <zh...@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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org
> For additional commands, e-mail: dev-help@brpc.apache.org
>
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by 牟盖东 <mo...@gmail.com>.
OK, I agree that we keep a stabe release schedule.
tan zhongyi <zh...@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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org
> For additional commands, e-mail: dev-help@brpc.apache.org
>
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by tan zhongyi <zh...@gmail.com>.
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，“牟盖东”<mo...@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 <zh...@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 <zh...@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-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by 牟盖东 <mo...@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 <zh...@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 <zh...@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
>
Re: How about we make our release more regularly? For example, one
version for one quarter
Posted by JiashunZhu <zh...@gmail.com>.
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 <zh...@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