?????? [DISCUSSSION]about servicecomb java chassis release plan

[bismy]

I explained in short 'In order to meet customers requirements of continuous 
intergration'.  
The vote process takes too long time, for emergency customer needs, we can't 
wait the vote process. 




------------------ ???????? ------------------
??????:                                                                         
                                               "dev"                            
                                                        
<willem.ji...@gmail.com&gt;;
????????:&nbsp;2021??2??10??(??????) ????11:11
??????:&nbsp;"dev"<dev@servicecomb.apache.org&gt;;

????:&nbsp;Re: [DISCUSSSION]about servicecomb java chassis release plan



If we just add a tag on the branch without the vote we cannot call it
a release.
Could you explain why you are doing this?

Willem Jiang

Twitter: willemjiang
Weibo: ????willem

On Tue, Feb 9, 2021 at 5:47 PM bismy <bi...@qq.com&gt; wrote:
&gt;
&gt; Hi all,&amp;nbsp;
&gt;
&gt;
&gt; In order to meet customers requirements of continuous intergration, I am 
going to change the schedule of java chassis release plan. As&amp;nbsp;
&gt;
&gt;
&gt; 1. release minor versions without vote and no RN is provided. e.g. I will 
release 2.1.6, 2.1.7, etc at any possible time without the vote process, and no 
RN is provided. I only add a tag in github.&amp;nbsp;
&gt; 2. release major versions in about 2~3 months, and the process is the same 
as we did before. e.g. I will release 2.2.0 according to the release schedule 
in JIRA, and vote before release this version.&amp;nbsp;
&gt; &amp;nbsp; And I will add release notes from 2.1.5 to 2.2.0.&amp;nbsp;
&gt;
&gt;
&gt; Please feedback if you got any questions.&amp;nbsp;