Re: Updating Javascript npm Package

[Igor Sapego <is...@apache.org>]

Kevin,

Basically, to change this we need people who would actively drive
development of the client and be active community members.

Best Regards,
Igor


On Mon, Sep 27, 2021 at 6:02 PM Ivan Daschinsky <iv...@gmail.com> wrote:

> Hi! I can share my experience how to drive this activity. Personally, I've
> driven four recent releases of python thin client (pyignite). First of all,
> you should start a discussion, this thread is a good place to start.
> Secondly, you should prepare release branch (with help of commiters),
> create realease notes, etc. Secondly, PMC member should prepare rc
> artifact, sign with signature, theb publish it in apache svn for voting.
> After successful voting, release artifact can be published to npmjs.
>
> Let's start this activity!
>
> пн, 27 сент. 2021 г., 18:52 Kevin Corbett <ke...@gridgain.com>:
>
>> Hello Igniters!
>>
>> I’ve been helping with the Ignite social media channels for the last
>> month now. Lately I’ve been trying to increase awareness of our Javascript
>> capabilities, namely the thin client. Someone on our Twitter page had
>> mentioned the npm package hasn’t been updated in 3 years (!)
>>
>> I see our Github for the thin client was last updated in January this
>> year. What can we do to get this updated?
>> https://www.npmjs.com/package/apache-ignite-client <
>> https://www.npmjs.com/package/apache-ignite-client>
>>
>> Also, I saw there was an attempt to add Apache Ignite support to TypeORM
>> but there were many issues with the client.
>> https://github.com/typeorm/typeorm/pull/7012
>
>