Re: ECharts incubator report
Using "rc" tag for release candidates seems to be a reasonable choice, in which case developers need to explicitly use "npm install echarts@rc" to use the rc version. I think Justin has no objection to this, right? But our main controversy lies on what to do with v4.2.0-rc1, which has already been published to "latest" and can be accessed by "npm install". The reasons were stated clearly in previous emails. We would like to get some advice from mentors that whether there could be some way to prevent the mess caused by unpublishing an rc version without a new correct version, and whether it is necessary for us to ask ASF board about it. Zhang Wenli http://zhangwenli.com On Sun, Feb 3, 2019 at 1:40 PM Dave Fisher wrote: > Please do not use Cordova as an example of a conforming project. > > Let’s discuss how to properly use of npm and staying where snapshots > require explicit user choice. > > Regards, > Dave > > Sent from my iPhone > > > On Feb 2, 2019, at 3:52 PM, Clement Ho > wrote: > > > > I just want to note that another popular apache project, cordova seems to > > publish nightly builds to npm ( > > https://www.npmjs.com/package/cordova) > > > > But it does look like the ‘latest’ tag is always set to the approved > > release for public use. Perhaps echarts can mimic their exact model? > > > > Clement > > > >> On Sun, Feb 3, 2019 at 7:28 AM Justin Mclean > wrote: > >> > >> Hi, > >> > >> I can see that nothing has been done about [1]. The PPMC cannot provide > >> unapproved releases to the general public in this manner. [2] All > releases > >> must be approved by the PPMC and IPMC while in incubation. As the VP of > the > >> Apache Incubator I'm asking you to please remove this unapproved release > >> and any others you have made public since starting graduation. > >> > >> If you can come up with another solution that complies with the ASF > >> release policy I'm willing to listen to it. > >> > >> Thanks, > >> Justin > >> V.P. Incubator > >> > >> 1. https://www.npmjs.com/package/echarts > >> 2. http://www.apache.org/legal/release-policy.html#release-approval > >> > >> - > >> 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 > >
Re: ECharts incubator report
Please do not use Cordova as an example of a conforming project. Let’s discuss how to properly use of npm and staying where snapshots require explicit user choice. Regards, Dave Sent from my iPhone > On Feb 2, 2019, at 3:52 PM, Clement Ho wrote: > > I just want to note that another popular apache project, cordova seems to > publish nightly builds to npm ( > https://www.npmjs.com/package/cordova) > > But it does look like the ‘latest’ tag is always set to the approved > release for public use. Perhaps echarts can mimic their exact model? > > Clement > >> On Sun, Feb 3, 2019 at 7:28 AM Justin Mclean wrote: >> >> Hi, >> >> I can see that nothing has been done about [1]. The PPMC cannot provide >> unapproved releases to the general public in this manner. [2] All releases >> must be approved by the PPMC and IPMC while in incubation. As the VP of the >> Apache Incubator I'm asking you to please remove this unapproved release >> and any others you have made public since starting graduation. >> >> If you can come up with another solution that complies with the ASF >> release policy I'm willing to listen to it. >> >> Thanks, >> Justin >> V.P. Incubator >> >> 1. https://www.npmjs.com/package/echarts >> 2. http://www.apache.org/legal/release-policy.html#release-approval >> >> - >> 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
Re: ECharts incubator report
Thanks Justin. I think we should probably ask the ASF board about this. In the meantime, could our mentors give some advice and opinions on this? Zhang Wenli http://zhangwenli.com On Sun, Feb 3, 2019 at 12:32 PM Justin Mclean wrote: > Hi, > > I sorry but what npm recommends is nothing to do with ASF release policy. > > > On the other hand, if a version is deprecated, it will give a warning to > tell > > the developers to update, which, in our case, is somewhat strange since > we > > don't have a newer correct version. > > Yes that is unfortunate but you need to follow ASF release policy. If you > want an exception to this then you need to ask the ASF board. > > > So, the safest and best-for-all solution seems to be, releasing a correct > > version with the permission of PPMC ASAP, which we are working on > > currently. And after that, mark the 4.2.0-rc1 to be deprecated. > > I don't think that is the best course of action but discuss with your > mentors and see what they say. > > > I think this way also benefits Apache's branding in saving a large number > > of developers' confusion and complaints. > > Could @Justin please help judge if this works with Apache? > > By putting out unapproved released you put the legal protections that the > ASF have in place for your project and the ASF itself at risk. It's > probably not a large risk but it's there all the same. Please read [1] so > you understand why the ASF has a release policy and why we don't allow > unapproved releases. > > Thanks, > Justin > > 1. http://www.apache.org/legal/release-policy.html#why > > - > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > For additional commands, e-mail: dev-h...@echarts.apache.org > >
Re: ECharts incubator report
In my prior experience working with unpublishing npm packages, the npm support team will only let you deprecate packages when you are within a certain download volume - which I think echarts would fit in that category. At GitLab (where I work), we had to deprecate vs unpublishing and we had a lower weekly download count than echarts. On Sun, Feb 3, 2019 at 12:32 PM Justin Mclean wrote: > Hi, > > I sorry but what npm recommends is nothing to do with ASF release policy. > > > On the other hand, if a version is deprecated, it will give a warning to > tell > > the developers to update, which, in our case, is somewhat strange since > we > > don't have a newer correct version. > > Yes that is unfortunate but you need to follow ASF release policy. If you > want an exception to this then you need to ask the ASF board. > > > So, the safest and best-for-all solution seems to be, releasing a correct > > version with the permission of PPMC ASAP, which we are working on > > currently. And after that, mark the 4.2.0-rc1 to be deprecated. > > I don't think that is the best course of action but discuss with your > mentors and see what they say. > > > I think this way also benefits Apache's branding in saving a large number > > of developers' confusion and complaints. > > Could @Justin please help judge if this works with Apache? > > By putting out unapproved released you put the legal protections that the > ASF have in place for your project and the ASF itself at risk. It's > probably not a large risk but it's there all the same. Please read [1] so > you understand why the ASF has a release policy and why we don't allow > unapproved releases. > > Thanks, > Justin > > 1. http://www.apache.org/legal/release-policy.html#why > > - > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > For additional commands, e-mail: dev-h...@echarts.apache.org > >
Re: ECharts incubator report
Hi, I sorry but what npm recommends is nothing to do with ASF release policy. > On the other hand, if a version is deprecated, it will give a warning to tell > the developers to update, which, in our case, is somewhat strange since we > don't have a newer correct version. Yes that is unfortunate but you need to follow ASF release policy. If you want an exception to this then you need to ask the ASF board. > So, the safest and best-for-all solution seems to be, releasing a correct > version with the permission of PPMC ASAP, which we are working on > currently. And after that, mark the 4.2.0-rc1 to be deprecated. I don't think that is the best course of action but discuss with your mentors and see what they say. > I think this way also benefits Apache's branding in saving a large number > of developers' confusion and complaints. > Could @Justin please help judge if this works with Apache? By putting out unapproved released you put the legal protections that the ASF have in place for your project and the ASF itself at risk. It's probably not a large risk but it's there all the same. Please read [1] so you understand why the ASF has a release policy and why we don't allow unapproved releases. Thanks, Justin 1. http://www.apache.org/legal/release-policy.html#why - To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org For additional commands, e-mail: dev-h...@echarts.apache.org
Re: ECharts incubator report
Thanks Clement. Yes, I think we and Justin have reached such a consensus that we should use npm tag for rc releases. What we are discussing about is what we should do to the previous version 4.2.0-rc1, which was published without the rc tag since we didn't know the method yet. Zhang Wenli http://zhangwenli.com On Sun, Feb 3, 2019 at 7:52 AM Clement Ho wrote: > I just want to note that another popular apache project, cordova seems to > publish nightly builds to npm ( > https://www.npmjs.com/package/cordova) > > But it does look like the ‘latest’ tag is always set to the approved > release for public use. Perhaps echarts can mimic their exact model? > > Clement > > On Sun, Feb 3, 2019 at 7:28 AM Justin Mclean wrote: > > > Hi, > > > > I can see that nothing has been done about [1]. The PPMC cannot provide > > unapproved releases to the general public in this manner. [2] All > releases > > must be approved by the PPMC and IPMC while in incubation. As the VP of > the > > Apache Incubator I'm asking you to please remove this unapproved release > > and any others you have made public since starting graduation. > > > > If you can come up with another solution that complies with the ASF > > release policy I'm willing to listen to it. > > > > Thanks, > > Justin > > V.P. Incubator > > > > 1. https://www.npmjs.com/package/echarts > > 2. http://www.apache.org/legal/release-policy.html#release-approval > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > > For additional commands, e-mail: dev-h...@echarts.apache.org > > > > >
Re: ECharts incubator report
Hi Justin, We are willing to deal with the latest released rc version problem. As we can see from npm documentation [1], unpublishing is "generally considered bad behavior to remove versions of a library that others are depending on". And in our case, it is even more dangerous since ECharts has more than 70,000 downloads, and we haven't provided a correct version after that. It's recommended to mark the previous rc version to be deprecated rather than unpublish it [1][2]. And please note that > With the default registry (registry.npmjs.org), unpublish is only allowed > with versions published in the last 72 hours. If you are trying to > unpublish a version published longer ago than that, contact > supp...@npmjs.com. [1] When a version is unpublished, if some projects have something like `"echarts": "^4.2.0-rc1"` in their package.json, it will cause an error in `npm install` step and bring confusion to a great number of developers. On the other hand, if a version is deprecated, it will give a warning to tell the developers to update, which, in our case, is somewhat strange since we don't have a newer correct version. So, the safest and best-for-all solution seems to be, releasing a correct version with the permission of PPMC ASAP, which we are working on currently. And after that, mark the 4.2.0-rc1 to be deprecated. And we promise that all rc releases under npm in the future should go with "rc" tag to prevent it from being "latest", and the default install way "npm install" will use the latest version permitted by PPMC. I think this way also benefits Apache's branding in saving a large number of developers' confusion and complaints. Could @Justin please help judge if this works with Apache? BTW, we are going to have Chinese New Year from tomorrow till next week, so slow email response is expected. Sorry for the inconvenience, and wish you a happy new year! [1] https://docs.npmjs.com/cli/unpublish [2] https://docs.npmjs.com/cli/deprecate Zhang Wenli http://zhangwenli.com On Sun, Feb 3, 2019 at 7:28 AM Justin Mclean wrote: > Hi, > > I can see that nothing has been done about [1]. The PPMC cannot provide > unapproved releases to the general public in this manner. [2] All releases > must be approved by the PPMC and IPMC while in incubation. As the VP of the > Apache Incubator I'm asking you to please remove this unapproved release > and any others you have made public since starting graduation. > > If you can come up with another solution that complies with the ASF > release policy I'm willing to listen to it. > > Thanks, > Justin > V.P. Incubator > > 1. https://www.npmjs.com/package/echarts > 2. http://www.apache.org/legal/release-policy.html#release-approval > > - > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > For additional commands, e-mail: dev-h...@echarts.apache.org > >
Re: ECharts incubator report
I just want to note that another popular apache project, cordova seems to publish nightly builds to npm ( https://www.npmjs.com/package/cordova) But it does look like the ‘latest’ tag is always set to the approved release for public use. Perhaps echarts can mimic their exact model? Clement On Sun, Feb 3, 2019 at 7:28 AM Justin Mclean wrote: > Hi, > > I can see that nothing has been done about [1]. The PPMC cannot provide > unapproved releases to the general public in this manner. [2] All releases > must be approved by the PPMC and IPMC while in incubation. As the VP of the > Apache Incubator I'm asking you to please remove this unapproved release > and any others you have made public since starting graduation. > > If you can come up with another solution that complies with the ASF > release policy I'm willing to listen to it. > > Thanks, > Justin > V.P. Incubator > > 1. https://www.npmjs.com/package/echarts > 2. http://www.apache.org/legal/release-policy.html#release-approval > > - > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > For additional commands, e-mail: dev-h...@echarts.apache.org > >
Re: ECharts incubator report
Hi, I can see that nothing has been done about [1]. The PPMC cannot provide unapproved releases to the general public in this manner. [2] All releases must be approved by the PPMC and IPMC while in incubation. As the VP of the Apache Incubator I'm asking you to please remove this unapproved release and any others you have made public since starting graduation. If you can come up with another solution that complies with the ASF release policy I'm willing to listen to it. Thanks, Justin V.P. Incubator 1. https://www.npmjs.com/package/echarts 2. http://www.apache.org/legal/release-policy.html#release-approval - To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org For additional commands, e-mail: dev-h...@echarts.apache.org
[GitHub] azpublic opened a new issue #9890: Synchronize tooltip between two charts (grid)
azpublic opened a new issue #9890: Synchronize tooltip between two charts (grid)
URL: https://github.com/apache/incubator-echarts/issues/9890
## General Questions
## Issue Type
- [ x] I have a question to ask about *how to use ECharts to ...*；我想提问如何使用
ECharts 实现某功能
- [ ] I have a bug to report；我想要报 bug
- [ ] I have a feature to request, e.g.: *I'd like a new feature that
...*；我需要一个新功能
- [ ] I have a feature to enhance, e.g.: *The current feature should be
improved in the way that ...*；我希望改进某个功能
- [ ] There's something wrong with the documents；文档有些问题
- [ ] Others, or I'm not sure which issue types to choose
here；其他，或我不知道应该选什么类型
## Issue Details
I would like to know if it is possible to have a synchronized tooltip
between two grid elements.
### Expected Behavior
When moving the mouse on my candlestick chart I would like the cross
tooltip to move simultaneously to the corresponding X axis position of the
other chart (2nd grid element) that is located right below. They share the same
X axis data (dates). Is this possible in any way?
Thanks !
### Current Behavior
Current behavior is that the cursor and tooltip only moves on the chart
that the mouse is hovering.
Ideally the seccond chart would display the tooltip and cross too at the
same time.
### Online Example
## Topics
## Anything Else We Need to Know
## Environment
- ECharts version；ECharts 版本: {DESCRIBE_HERE}
- [ ] It happens only on certain browsers or operating systems.
对于特定浏览器或操作系统才会出现的问题，请提供相应环境信息：{BROWSER_VERSION_OR_OS_INFORMATION_HERE}
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
For additional commands, e-mail: dev-h...@echarts.apache.org
