Thanks Dave. BTW, do you have the auth to stop the Gitbox sending notifications to dev@ ?
2018-04-17 14:03 GMT+08:00 Dave Fisher <dave2w...@comcast.net>: > Hi - > > Sent from my iPhone > > > On Apr 16, 2018, at 10:49 PM, SHUANG SU <sushuang0...@gmail.com> wrote: > > > > Hi Dave, > > > >> (1) Due to the world wide / volunteer nature of an Apache project VOTEs > > require a minimum of 72 hours. > >> (2) In the Incubator each release will often require two votes. > > > > Should the two votes be parallel or sequentially? If sequentially, the > two > > votes will take 72 * 2 = 6 days, about one week? (I am worried that it is > > too long. 3 days probably be reasonable.) > > These are sequential. Six days is a minimum. Once eCharts graduates it > will be 3 days. > > > > > > > And, @Shenyi and @Wenli, > > I think we may take advantage of the procedure of the 72 hours, if the > tag > > to be released can be traded as a "beta version", can be tested by > > volunteers, and eliminate "recovery build" we used to face. > > But, if possible, how the tag to be released can be downloaded by > > volunteers? Should we provide the "download of beta" in echarts website? > > The volunteers test the release candidate and VOTE on the result on the > dev@ list. This is normal. The release candidate is tested to make sure > it meets both project quality standards and Apache legal standards. > > This should all be discussed on this list! > > Regards, > Dave > > > > > > > > > > > > 2018-04-17 12:24 GMT+08:00 Dave Fisher <dave2w...@comcast.net>: > > > >> Hi Wenli, > >> > >> With my mentor hat you should know that in the Incubator it is hard to > >> predict how long it will take to do a release. > >> > >> A few standards apply: > >> > >> (1) Due to the world wide / volunteer nature of an Apache project VOTEs > >> require a minimum of 72 hours. > >> > >> (2) In the Incubator each release will often require two votes. First in > >> podling and second on general@. Often the Incubator vote takes longer. > >> This time can only be compressed if there are three votes from the > mentors > >> on the initial vote. > >> > >> The website can and should proceed in parallel to a release. If timing > >> works then they are simultaneous, but it is nit needed. Either can > finish > >> first. > >> > >> Regards, > >> Dave > >> > >> Sent from my iPhone > >> > >>> On Apr 16, 2018, at 8:29 PM, Wenli Zhang <oviliazh...@gmail.com> > wrote: > >>> > >>> Hi all, > >>> > >>> We'd like to vote for the release time of next ECharts version. > >>> > >>> Plan A: Wait for echarts.apache.org to be ready. > >>> This may take about one week or more. > >>> > >>> Plan B: Release it ASAP. (Perhaps on Wednesday.) > >>> This is because last release was on 28th Feb, and may bugs have been > >> fixed > >>> since then. > >>> > >>> Please reply +1 if you prefer Plan A. > >>> > >>> Zhang Wenli > >>> http://zhangwenli.com > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > >> For additional commands, e-mail: dev-h...@echarts.apache.org > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > For additional commands, e-mail: dev-h...@echarts.apache.org > >
