ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Pavlov <dpavlov....@gmail.com>
Subject Re: Postpone Apache Ignite 2.5 release to fix baseline topology
Date Sat, 28 Apr 2018 15:08:23 GMT
I like AI 2.5 now, but then release AI 2.6 with (BL)AT fix. Probably we
will find some more changes to be delivered to users.

сб, 28 апр. 2018 г. в 17:56, Vladimir Ozerov <vozerov@gridgain.com>:

> Yakov,
>
> Messages would help users understand what is wrong earlier, but will not
> protect them from additional maintenance which is required in AI 2.4 and is
> supposed to be removed in next AI releases.
> Please note that in IEP-4 topic I proposed alternative solution - release
> AI 2.5 now, but then release AI 2.6 as soon as BLT is fixed. I.e. it would
> be emergency release.
>
> Both approaches works for me, the main goal is to deliver original defaults
> ASAP. However, approach with a single release looks better to me because it
> will minimize number of migrations for users.
>
> Vladimir.
>
>
> On Sat, Apr 28, 2018 at 5:47 PM, Yakov Zhdanov <yzhdanov@apache.org>
> wrote:
>
> > Guys, how about we release 2.5 in the nearest future after adding proper
> > usability log messages that will explain user what to do and also output
> > link to readme.io with the first BLT related message during node uptime.
> > This should not take much time and we can use the same messages when we
> > have (BL)AT modes in 2.6. I think that adding messages makes sense and
> > should be clear for users which is not the case for 2.4.
> >
> > --Yakov
> >
>

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