Thin client protocol version release notes.

[Igor Sapego <is...@gridgain.com>]

Igniters,

Currently, our thin client specification is kept on readme.io [1].
However, sometimes to introduce new features while keeping
backward compatibility, we need to increase protocol version.

The issue is: there is currently no easy way for thin client
developers to find out when thin protocol version has been
updated and what kind of new features have been introduced.

We may want to make a rule, that a commiter, that merge a
commit to the master, that introduces new thin client version,
should send an update email to devlist.

We may also want to have some kind of "Changes list" page on
readme.io which will track protocol changes from version to
version.

What are your thoughts on the topic?

[1] - https://apacheignite.readme.io/docs/binary-client-protocol

Best Regards,
Igor

Re: Thin client protocol version release notes.

[Denis Magda <dm...@apache.org>]

The change list page is a good offer. As for the versions, it's clear that
the protocol version differs from an Ignite one. However, a next protocol
version officially becomes available with a next Ignite release meaning.
For me, it means, all the new protocol changes need to be documented on a
readme.io page for an upcoming release.

--
Denis

On Mon, Jun 4, 2018 at 3:54 AM, Igor Sapego <is...@gridgain.com> wrote:

> Igniters,
>
> Currently, our thin client specification is kept on readme.io [1].
> However, sometimes to introduce new features while keeping
> backward compatibility, we need to increase protocol version.
>
> The issue is: there is currently no easy way for thin client
> developers to find out when thin protocol version has been
> updated and what kind of new features have been introduced.
>
> We may want to make a rule, that a commiter, that merge a
> commit to the master, that introduces new thin client version,
> should send an update email to devlist.
>
> We may also want to have some kind of "Changes list" page on
> readme.io which will track protocol changes from version to
> version.
>
> What are your thoughts on the topic?
>
> [1] - https://apacheignite.readme.io/docs/binary-client-protocol
>
> Best Regards,
> Igor
>

Re: Thin client protocol version release notes.

[Pavel Petroshenko <pa...@petroshenko.com>]

Hi Igor,

That's a great idea! This would make the client developers' lives much
easier.

Pavel

On Mon, Jun 4, 2018 at 3:54 AM, Igor Sapego <is...@gridgain.com> wrote:

> Igniters,
>
> Currently, our thin client specification is kept on readme.io [1].
> However, sometimes to introduce new features while keeping
> backward compatibility, we need to increase protocol version.
>
> The issue is: there is currently no easy way for thin client
> developers to find out when thin protocol version has been
> updated and what kind of new features have been introduced.
>
> We may want to make a rule, that a commiter, that merge a
> commit to the master, that introduces new thin client version,
> should send an update email to devlist.
>
> We may also want to have some kind of "Changes list" page on
> readme.io which will track protocol changes from version to
> version.
>
> What are your thoughts on the topic?
>
> [1] - https://apacheignite.readme.io/docs/binary-client-protocol
>
> Best Regards,
> Igor
>