Dear mentors, We've published our release vote on general@, but it has got no reply by now. Could you have a look at it, and give a +1 perhaps?
Zhang Wenli http://zhangwenli.com On Wed, Jan 30, 2019 at 11:34 PM Dave Fisher <[email protected]> wrote: > Hi - > > Also, the project did begin discussions about adding a committer on > private@. These stalled, but can be restarted now. > > Regards, > Dave > > Sent from my iPhone > > > On Jan 30, 2019, at 7:24 AM, Kevin A. McGrail <[email protected]> > wrote: > > > > Nice response Shuang. If I can help with the voting process for > > releases, etc., please let me know. > > > > I can also try to help with adding more committers, writing notices, > > etc. to try and get more interest on Social Media even. > > > > Regards, > > KAM > >> On 1/30/2019 3:11 AM, SHUANG SU wrote: > >> Hi Justin, > >> > >> I am afraid it is inevitable to push the rc version to npm. Without > that, > >> the build > >> process and some local CI process can not be performed, which causes the > >> developers > >> concerning about this project can not test whether the release > candidate is > >> qualified to be released. > >> But the rc version is not tagged as "latest" in npm, so the public can > not > >> get this version > >> by `npm install`. So it will not make bad effect, just like publishing > the > >> rc pack to the > >> Apache svn dev repo [1]. > >> > >> But the published `4.2.0-rc.2` on npm you saw in [2] is tagged as > "latest" > >> and have been > >> published to the public. That is incorrect according to the Apache > rule. We > >> should have > >> removed it. But unfortunately we have missed the opportunity to do that. > >> Many outsider > >> projects or systems have depended on that, and the removal will cause > some > >> disaster. > >> > >> This mistake was made because we did not clear enough about the total > >> release process. > >> But having this experience, this mistake will not happen again. Only the > >> official release > >> will be directed to publish in npm from now on. > >> > >> 1. https://dist.apache.org/repos/dist/dev/incubator/ > >> 2. https://www.npmjs.com/package/echarts > >> > >> > >> Thanks > >> > >> ------------------------------ > >> Su Shuang (100pah) > >> ------------------------------ > >> > >> > >> > >>> On Wed, 30 Jan 2019 at 15:14, Justin Mclean <[email protected]> > wrote: > >>> > >>> HI, > >>> > >>>> As about "When were the last committers or PPMC members elected?", we > >>> don't have new committers or PPMC members elected after the > initiation. So > >>> should I fill in NA or the initiation date? > >>> > >>> Yes, but being a year in incubation without adding any committer or PMC > >>> members is concerning, especially given the number of contributors to > the > >>> project. You might want to put in the report what is being done to > address > >>> this.There’s some tasks mentioned on the private list that need to be > >>> followed up on by the PPMC I think. > >>> > >>>> As about release version, we tagged "rc" for release candidate > version. > >>> Does that mean rc version can never be available to the public? > >>> > >>> Release candidates should not be made available to the general public, > >>> they can be made available to people who follow the dev list. [1] They > can > >>> be placed here. [2] > >>> > >>> Thanks, > >>> Justin > >>> > >>> 1. https://www.apache.org/dev/release-distribution#unreleased > >>> 2. http://www.apache.org/legal/release-policy.html#stage > >>> > >>> > >>> > > > > -- > > Kevin A. McGrail > > VP Fundraising, Apache Software Foundation > > Chair Emeritus Apache SpamAssassin Project > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > >
