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
> > > >
> > >
> >
>

Reply via email to