Hi Vitalii,

Thanks for being interested in Apache ECharts. This project is maintained
mostly by the community, so we can't and don't wish to push our
contributors to follow a restricted release plan. Our Project Management
Committee members review the pull request regularly so the fastest way to
solve your bugs or new features is to make a pull request.
As you may know, Apache ECharts has many users (its weekly download
amount is 400,000 on npm). So if you wait for the community to solve your
issues, it may take a long time. If you are interested in making a pull
request but have questions about the technical details, you are welcomed to
discuss with the community in the pull request. I have too many
notifications on GitHub so sometimes I miss some information. If you have
urgent questions, please send us an email on the mailing list. We are
willing to help you out.

Thanks

*Ovilia*


On Fri, Sep 15, 2023 at 6:52 AM Kravchenko, Vitalii
<vitalii.kravche...@jpmorgan.com.invalid> wrote:

> Hi,
>
> We have recently adopted eCharts as the charting solution for our project
> but it seems like eCharts’ development has cooled off a lot in recent
> months, looking at the number of commits in the master branch:
> https://github.com/apache/echarts/commits/master
>
> We are very happy and impressed with the library generally and grateful
> that such a product exists but there are a few minor things here and there
> that we’d like to see fixed. For example:
> https://github.com/apache/echarts/issues/created_by/yay
>
> Could you please shed some light on where you guys are with eCharts
> development? Are you taking a break, or is it in maintenance mode now, and
> if I should submit my contributions for you to review?
>
> Thank you,
> Vitalii Kravchenko
>
> This message is confidential and subject to terms at:
> https://www.jpmorgan.com/emaildisclaimer including on confidential,
> privileged or legal entity information, malicious content and monitoring of
> electronic messages. If you are not the intended recipient, please delete
> this message and notify the sender immediately. Any unauthorized use is
> strictly prohibited.
>

Reply via email to