Hi Denis, Here are the links to the instructions on how to release new versions for the clients: Python - [1], Node.JS - [2], PHP - [3].
[1] http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Apache-Ignite-2-7-0-Release-RC2-tt38862.html#a39339 [2] https://github.com/nobitlost/ignite/tree/ignite-7777-docs/modules/platforms/nodejs#publish-ignite-nodejs-client-on-npmjscom-instruction [3] https://github.com/nobitlost/ignite/tree/ignite-7783-docs/modules/platforms/php#release-the-client-in-the-php-package-repository-instruction Regards, Pavel On Tue, Jun 25, 2019 at 2:54 PM Denis Magda <[email protected]> wrote: > Dmitry, thanks for starting the conversation. > > Generally speaking, there are two outstanding items: > > - Npm (NodeJS), pip (Python) and composer (PHP) update instructions > need to be added to the release process page. Nuget (.NET) is a good > reference [1]. @Alexey Kosenchuk <[email protected]>, @Pavel > Petroshenko <[email protected]> could you please help with this? I > have a feeling you shared this instruction before, but it might have been > lost in dev list archives. Apologize for that. > - Python, NodeJS and PHP API Docs need to be uploaded to Ignite > website for every release the way similar to languages like Java [2] or C++ > [3] > > As for the current release, have we ensured that the thin clients that are > already uploaded to npm, pip, and composer would work with 2.7.5? If the > answer is positive, then, yes, let's skip this test. Going forward, we'll > discuss decoupling of thin clients and the core. > > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.3.13.UploadNuGetpackagestonuget.org > [2] https://ignite.apache.org/releases/latest/javadoc/index.html > [3] https://ignite.apache.org/releases/latest/cppdoc/index.html > > > - > Denis > > > On Tue, Jun 25, 2019 at 10:12 AM Igor Sapego <[email protected]> wrote: > >> Ilya, >> >> Examples are not part of the packet. I can not see any other changes >> in thin clients in question, so I don't think any actions are required for >> this release. >> >> Dmitry, >> >> Well, yeah, they have separate versions. I believe, they should be >> included >> in our release process, just like a nuget for .net, but in this particular >> case >> no actions are required from us. >> >> Best Regards, >> Igor >> >> >> On Tue, Jun 25, 2019 at 4:52 PM Ilya Kasnacheev < >> [email protected]> >> wrote: >> >> > Hello! >> > >> > I remember that we have fixed Python examples being empty, so Python >> should >> > probably be re-released. >> > >> > Regards, >> > -- >> > Ilya Kasnacheev >> > >> > >> > вт, 25 июн. 2019 г. в 15:54, Dmitriy Pavlov <[email protected]>: >> > >> > > Hi Igor, >> > > >> > > You can find the list here >> > > >> > > >> > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.5#ApacheIgnite2.7.5-Resolvedtickets >> > > Release notes: >> > https://ignite.apache.org/releases/2.7.5/release_notes.html >> > > >> > > Are these clients released independently? and have their own version? >> > > >> > > Sincerely, >> > > Dmitriy Pavlov >> > > >> > > >> > > вт, 25 июн. 2019 г. в 15:28, Igor Sapego <[email protected]>: >> > > >> > > > Dmitry, do you have a list of tickets for this release? >> > > > I'm not sure if any client was changed and required a separate >> release. >> > > > >> > > > Best Regards, >> > > > Igor >> > > > >> > > > >> > > > On Tue, Jun 25, 2019 at 10:47 AM Dmitriy Pavlov <[email protected] >> > >> > > > wrote: >> > > > >> > > > > Hi Igniters, >> > > > > >> > > > > Denis M. asked me if we should release some packages for thin >> > clients. >> > > Is >> > > > > it released as part of Ignite? Alternatively, is it released in an >> > > > > independent cycle? >> > > > > >> > > > > It is missed in >> > > > > >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process >> > so >> > > I >> > > > > ask contributors or experts to provide some information on how to >> > > release >> > > > > it (in both cases if it is independent or not). >> > > > > >> > > > > 2.7.5 does not have huge API changes, so all clients should be >> > > > compatible. >> > > > > >> > > > > Sincerely >> > > > > Dmitriy Pavlov >> > > > > >> > > > >> > > >> > >> >
