Amazing Job! My vote is +1 binding
- The release file is in the right location - Signature and hash are correct. - Version is correct in package.json - Can build from source. - LICENSE and NOTICE files exist - NOTICE year correct On Mon, Jul 28, 2025 at 2:53 AM SHUANG SU <sushuang0...@gmail.com> wrote: > > I checked: > > - The release file is in the right location. > > - sha512 and asc is correct. > > - Version is correct in package.json and src/core/echarts.ts . > > - The source code is the same as the GitHub tag "5.6.0-rc.1". > > - The build result from the published source code is the same as npm > "5.6.0-rc.1". > > - The diff from tag "5.6.0-rc.1" to the last tag is OK. > > - LICENSE is correct. > > - RELEASE_NOTE exists and is correct. > > - Download and npm install and build OK. > > - Can run examples from build. > > > Sorry I used the old email template and forgot to change the version > number. > Edit to my previous post: > > +1 (binding) > > I checked: > - The release file is in the right location. > - sha512 and asc is correct. > - Version is correct in package.json and src/core/echarts.ts . > - The source code is the same as the GitHub tag "6.0.0-rc.2". > - The build result from the published source code is the same as npm > "6.0.0-rc.2". > - The diff from tag "6.0.0-rc.2" to the last tag is OK. > - LICENSE is correct. > - RELEASE_NOTE exists and is correct. > - Download and npm install and build OK. > - Can run examples from build. > > Thanks, > ------------------------------ > Su Shuang (100pah) > ------------------------------ > > > > On Mon, 28 Jul 2025 at 02:46, SHUANG SU <sushuang0...@gmail.com> wrote: > > > +1 (binding) > > > > I checked: > > - The release file is in the right location. > > - sha512 and asc is correct. > > - Version is correct in package.json and src/core/echarts.ts . > > - The source code is the same as the GitHub tag "5.6.0-rc.1". > > - The build result from the published source code is the same as npm > > "5.6.0-rc.1". > > - The diff from tag "5.6.0-rc.1" to the last tag is OK. > > - LICENSE is correct. > > - RELEASE_NOTE exists and is correct. > > - Download and npm install and build OK. > > - Can run examples from build. > > > > > > > > Thanks, > > ------------------------------ > > Su Shuang (100pah) > > ------------------------------ > > > > > > > > On Thu, 24 Jul 2025 at 17:33, Ovilia <oviliazh...@gmail.com> wrote: > > > >> Dear community, > >> > >> We are pleased to be calling this vote for the release of Apache ECharts > >> 6.0.0 (release candidate 2). > >> > >> The release candidate to be voted over is available at: > >> https://dist.apache.org/repos/dist/dev/echarts/6.0.0-rc.2/ > >> > >> The release candidate is signed with a GPG key available at: > >> https://dist.apache.org/repos/dist/dev/echarts/KEYS > >> > >> The Git commit for this release is: > >> > >> > https://gitbox.apache.org/repos/asf?p=echarts.git;a=commit;h=52104f7daefb8d01ea809189dab81cadc874ce09 > >> > >> The Release Note is available in: > >> > https://dist.apache.org/repos/dist/dev/echarts/6.0.0-rc.2/RELEASE_NOTE.txt > >> > >> Build Guide: > >> https://github.com/apache/echarts/blob/6.0.0-rc.2/README.md#build > >> > >> NPM Install: > >> npm i echarts@6.0.0-rc.2 > >> https://www.npmjs.com/package/echarts/v/6.0.0-rc.2 > >> > >> Please vote on releasing this package as: > >> Apache ECharts 6.0.0 (release candidate 2) > >> by "2025-07-27T21:14:36.543Z". > >> > >> [ ] +1 Release this package > >> [ ] 0 I don't feel strongly about it, but don't object > >> [ ] -1 Do not release this package because... > >> > >> Anyone can participate in testing and voting, not just committers, > please > >> feel free to try out the release candidate and provide your votes. > >> > >> A checklist for reference: > >> > >> > https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Checklist > >> > >> Thanks > >> > >> *Ovilia* > >> > > > -- Yi Shen Apache ECharts PMC
