Is there a message thread or a link that I can use to learn more
information about this bug?

On Tue, Feb 26, 2019 at 2:54 PM SHUANG SU <[email protected]> wrote:

> Thanks Kevin an Dave for the vote and check.
>
> But I am very sorry that I have to close the vote, because someone just
> found a bug brought by the new version.
> It seems that the bug has to be fixed since it affects lots of usage
> scenarios.
> Fortunately, it is found in a rc version but not a formal release version.
>
> I will fix it and call a new rc vote soon.
>
>
> And by the way, the suggestion Dave given may be applied in the
> new rc version if we come to a conclusion:
>
> > Next release let’s discuss where the BSD License is placed. Since there
> is only one extra license the usual location is the end of the main LICENSE
> file. (Also the how to apply portion at the bottom of the LICENSE is not
> needed.)
>
> Will we move the content of the file "licenses/LICENSE-d3" to the end of
> the file "LICENSE"?
>
>
>
> ------------------------------
>  Su Shuang (100pah)
> ------------------------------
>
>
>
> On Tue, 26 Feb 2019 at 07:59, Dave Fisher <[email protected]> wrote:
>
> > [X] +1 Release this package (BINDING)
> >
> > I checked:
> > DISCLAIMER
> > LICENSE
> > NOTICE
> > Signature
> >  sha512 Hash
> > RAT Check passed.
> >
> > Next release let’s discuss where the BSD License is placed. Since there
> is
> > only one extra license the usual location is the end of the main LICENSE
> > file. (Also the how to apply portion at the bottom of the LICENSE is not
> > needed.)
> >
> > Here is how I performed a RAT Check:
> >
> > Previously I downloaded Apache RAT from creadur.apache.org
> >
> > java -jar ~/Development/apache-rat-0.12.jar .
> >
> > Regards,
> > Dave
> >
> > > On Feb 25, 2019, at 1:47 AM, SHUANG SU <[email protected]> wrote:
> > >
> > > I am pleased to be calling this vote for the release of Apache ECharts
> > > 4.2.1 (release candidate 2).
> > >
> > > The major update from 4.2.1 release candidate 1 to 2 is about the
> license
> > > statement.
> > > See more details in
> > >
> >
> https://lists.apache.org/thread.html/3817a70b2ec34a25b82f4a1310398ae9df8cdc6728fa289c941c5fde@%3Cdev.echarts.apache.org%3E
> > >
> > >
> > > The release candidate to be voted over is available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.2/
> > >
> > > The release candidate is signed with a GPG key available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> > >
> > > The Git commit for this release is:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=f2d76c9
> > >
> > > The Release Note is available in:
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.2/RELEASE_NOTE.txt
> > >
> > > Some shell commands for validating the release:
> > >
> > > ```shell
> > > # Download the release:
> > > curl
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.2/apache-echarts-4.2.1-rc.2-incubating-src.zip
> > > -o apache-echarts-4.2.1-rc.2-incubating-src.zip
> > > unzip apache-echarts-4.2.1-rc.2-incubating-src.zip -d
> > > apache-echarts-4.2.1-rc.2-incubating-src > /dev/null
> > >
> > > # Build the project (Node.js environment is required):
> > > cd "apache-echarts-4.2.1-rc.2-incubating-src" && npm install && cd ..
> > > node "apache-echarts-4.2.1-rc.2-incubating-src/build/build.js"
> --release
> > > # (See help: `node
> > > "apache-echarts-4.2.1-rc.2-incubating-src/build/build.js" --help`)
> > > ```
> > >
> > >
> > > Please vote on releasing this package as:
> > > Apache ECharts 4.2.1 (release candidate 2)
> > > by "2019-02-28T10:34:16.092Z".
> > >
> > > [ ] +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.
> > >
> > >
> > > ------------------------------
> > > Su Shuang (100pah)
> > > ------------------------------
> >
> >
>

Reply via email to