ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Goncharuk <alexey.goncha...@gmail.com>
Subject Re: [DiSCUSS] Incompatible changes
Date Wed, 26 Aug 2015 06:54:55 GMT
This particular change does not break the compatibility (a new method is
being added to the public API), however I am +1 for adding these principles
to the dev documentation.

2015-08-25 23:44 GMT-07:00 Konstantin Boudnik <cos@apache.org>:

> Reading this I thought it would be a good idea to articulate some of the
> possible challenges that we will face in the future.
>
> Say, how we add/release incompatible changes like API modifications,
> deprecations, etc. Say, introduction of incompatible changes shouldn't be
> done
> in minor release of a project: Scala "transition" 2.9 -> 2.10 comes to
> mind as
> a biggest screw-up of the kind. Hence, to avoid being a laughing stock of
> the
> world's developers it would makes perfect sense to have some of these
> seemingly obvious principles either written or referred among other
> development resources.
>
> Thoughts?
>     Cos
>
> On Tue, Aug 25, 2015 at 11:17PM, Alexey Goncharuk wrote:
> > Ken, I added comments to the pull request on GitHub.
> >
> > I would prefer another committer to review this pull request as well
> since
> > public API is being changed (Dmitriy, Yakov?)
> >
> > --
> > AG
> >
> > 2015-08-25 22:53 GMT-07:00 Ken Cheng <kcheng.mvp@gmail.com>:
> >
> > > Hi Devs,
> > >
> > > Anybody can help me to do a code review for PR
> > >
> > > https://github.com/apache/ignite/pull/35
> > >
> > > Thanks,
> > > kcheng
> > >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message