ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Zinoviev <zaleslaw....@gmail.com>
Subject Re: Proposed Release: 2.7.7 = 2.7.6 + ML + extra fixed bugs
Date Thu, 19 Sep 2019 14:52:28 GMT
No objection from my side if somebody could say that master is ready or
will be ready to release in a few months

чт, 19 сент. 2019 г. в 14:21, Nikolay Izhikov <nizhikov@apache.org>:

> +1 for 2.8 from me
>
> Scope:
>
> * master fixes
> * ML improvements
> * IEP-35: Metric + System views.
>
>
>
> В Чт, 19/09/2019 в 14:14 +0300, Pavel Tupitsyn пишет:
> > +1 for 2.8
> >
> > We should not hold master anymore, it has been a year already.
> >
> > On Thu, Sep 19, 2019 at 1:42 PM Dmitriy Pavlov <dpavlov@apache.org>
> wrote:
> >
> > > I like both options 2.7.7 & 2.8 both have their benefits.
> > >
> > > But someday we will anyway need to release master state. Let's not
> freeze
> > > master for years as Zookeeper did with 3.0.
> > >
> > > So I like option with 2.8 release more.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > чт, 19 сент. 2019 г. в 01:42, Denis Magda <dmagda@apache.org>:
> > >
> > > > Igniters,
> > > >
> > > > 2.8 release cycle can last for many months due to a number of issues
> and
> > > > regressions we need to address. It can easily slip to the next year,
> > > > especially considering the holiday season. An alternate solution can
> be a
> > > > series of Ignite 2.7.x releases that are becoming more hardened with
> each
> > > > version and go with a small and manageable changeset. For instance,
> ML
> > >
> > > and
> > > > Thin Clients optimizations with fixes for newly discovered critical
> > >
> > > issues
> > > > can be released in 2.7.7 and 2.7.8.
> > > >
> > > > As for 2.8, what exactly are we planning to release there?
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Wed, Sep 18, 2019 at 3:43 AM Nikolay Izhikov <nizhikov@apache.org
> >
> > > > wrote:
> > > >
> > > > > Start of December for 2.8 sounds good.
> > > > >
> > > > > В Ср, 18/09/2019 в 13:38 +0300, Alexey Zinoviev пишет:
> > > > > > Sounds good for me, I will be ready to release ML module till
1
> > > >
> > > > December
> > > > > > (end of September is not appropriate for ML module due to known
> > >
> > > issues
> > > > > and
> > > > > > bugs)
> > > > > > If the whole Ignite could be released to this date I will be
> happy in
> > > > > > another case I suggest the minor release by the formula mentioned
> > > >
> > > > above.
> > > > > >
> > > > > > Let's ask another module maintainers here?
> > > > > >
> > > > > > ср, 18 сент. 2019 г. в 13:00, Maxim Muzafarov <mmuzaf@apache.org
> >:
> > > > > >
> > > > > > > Folks,
> > > > > > >
> > > > > > > Agree, we should start a discussion about releasing Apache
> Ignite
> > >
> > > 2.8
> > > > > > > version right after 2.7.6 will be announced.
> > > > > > > Am I missing something?
> > > > > > >
> > > > > > > On Wed, 18 Sep 2019 at 12:33, Nikolay Izhikov <
> nizhikov@apache.org
> > > > > wrote:
> > > > > > > >
> > > > > > > > > of 2.7 release
> > > > > > > >
> > > > > > > > It's 2.8, of course. Sorry, for typo.
> > > > > > > >
> > > > > > > >
> > > > > > > > В Ср, 18/09/2019 в 12:36 +0300, Nikolay Izhikov
пишет:
> > > > > > > > > Hello, Alexey
> > > > > > > > >
> > > > > > > > > > we have no chance to
> > > > > > > > > > release the whole master branch
> > > > > > > > >
> > > > > > > > > Why do you think so?
> > > > > > > > > From my point of view, we should start discussion
of 2.7
> > >
> > > release,
> > > > > > >
> > > > > > > shortly(end of September of similar)
> > > > > > > > >
> > > > > > > > > В Ср, 18/09/2019 в 12:04 +0300, Alexey Zinoviev
пишет:
> > > > > > > > > > Dear Igniters, for the whole year I'm waiting
for the
> next
> > > > >
> > > > > release of
> > > > > > > > > > Apache Ignite with number 2.8 or 3.0. As
I understand we
> have
> > > >
> > > > no
> > > > > > >
> > > > > > > chance to
> > > > > > > > > > release the whole master branch, but we
have cool
> changes in
> > >
> > > ML
> > > > > > >
> > > > > > > component
> > > > > > > > > > that were not released since 2.7 (Nomember
2018).
> > > > > > > > > >
> > > > > > > > > > I'm ready to become a release manager of
the special
> release
> > > >
> > > > with
> > > > > > >
> > > > > > > the taste
> > > > > > > > > > of new ML by the formula: 2.7.6 plus new
ML plus all
> known
> > > >
> > > > fixed
> > > > > > >
> > > > > > > issues for
> > > > > > > > > > 2.7.6 release.
> > > > > > > > > >
> > > > > > > > > > Reason: ML has a limited dependency on core/sql
> component and
> > > > >
> > > > > could
> > > > > > >
> > > > > > > be
> > > > > > > > > > delivered without major changes in 2.7.6
> > > > > > > > > >
> > > > > > > > > > I hope to found the support from the community
side and
> maybe
> > > >
> > > > we
> > > > > > >
> > > > > > > deliver
> > > > > > > > > > another components like Thin Clients, Spark
integration
> and
> > > > >
> > > > > another
> > > > > > >
> > > > > > > ready
> > > > > > > > > > component without strong ties with core
component in the
> > >
> > > future
> > > > > > >
> > > > > > > according
> > > > > > > > > > this way (in release 2.7.9 for example)
> > > > > > > > > >
> > > > > > > > > > What do you think, Igniters?
>

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