ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Zinoviev <zaleslaw....@gmail.com>
Subject Re: Ignite 2.8 Release: Time & Scope & Release manager
Date Fri, 08 Mar 2019 10:29:36 GMT
I suggest to make a release from master but at 15 April-1 May to prepare
all release features. It's bad practice to announce release and cut master
in one week. And in future put the approximate date of release for feature
planning.

In ML we are in progress of changing API and it takes 1 month to stabilize
that and fix and we hope to deliver that functionality in 2.8.

чт, 7 марта 2019 г., 21:03 Denis Magda dmagda@apache.org:

> Dmitriy,
>
> Please find a copy-paste from the first conversation when impactful
> usability problems were reported more than a month ago:
>
> *I played with the latest Oracle JDK 11 on Mac OS Mojave. Results are sad:*
>
>    - *Starting a node from cmd (ignite.sh) - FAILED*
>    - *Opening Ignite examples - BAD EXPERIENCE*
>       - *pom.xml wasn't detected automatically, had to select it manually*
>       - *was hard to start the code samples (same issue as with cmd). As a
>       committer, I know how to fix it
>       (
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
>       <
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> >),
>       but most of the developers have no glue and will give up*
>       - *The step above have to be repeated for every single sample*
>
> Now, imagine that dozens of users new to Ignite go through this. Most of
> them will quit after the failures above and switch to an alternate solution
> - there are many choices depending on a use case.
>
> Give me a call if it still doesn't sound convincing to you. What I would
> do, considering Vladimirs's feedback, if the master is really in a bad
> shape then I would release 2.8 from 2.7 and 2.8.1, 2.8.2, etc. will be
> released from the master.
>
> -
> Denis
>
>
> On Thu, Mar 7, 2019 at 9:52 AM Dmitriy Pavlov <dpavlov@apache.org> wrote:
>
> > Denis, there is not so much difference in Java 9 vs Java 11, so previous
> > Java 9-efforts done by Igniters should be applicable for 11.
> >
> > So I don't understand why we can go through the normal release process
> and
> > pilot minor releases afterward. Please share a particular case when the
> > absence of `emergency 2.8` is a problem for the user.
> >
> > Is it still our rush and 'highway or no way'? I was in the hope it is
> gone.
> >
> > чт, 7 мар. 2019 г. в 20:43, Denis Magda <dmagda@apache.org>:
> >
> > > Vova,
> > >
> > > Thanks for the inputs. If it takes weeks to stabilize the master then
> > let's
> > > release from 2.7 cherry-picking Java 11 improvements. We can't wait for
> > > months holding these improvements - the world is switching to Java 11
> and
> > > Ignite fails during the first runs presently.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Thu, Mar 7, 2019 at 9:28 AM Vladimir Ozerov <vozerov@gridgain.com>
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > Making release from master is not an option. We have a lot of
> > > not-yet-ready
> > > > and not-yet-tested features. From SQL side this is partition pruning
> > and
> > > > SQL views with KILL command.
> > > >
> > > > So if we do not want to release a mess, then there are only two
> > options:
> > > > release Java 11 fixes on top of 2.7, or make normal release in about
> > > 1.5-2
> > > > month with proper feature freeze process and testing.
> > > >
> > > > Vladimir.
> > > >
> > > > чт, 7 марта 2019 г. в 20:10, Ilya Kasnacheev <
> > ilya.kasnacheev@gmail.com
> > > >:
> > > >
> > > > > Hello!
> > > > >
> > > > > Then please fast-forward review and merge
> > > > > https://issues.apache.org/jira/browse/IGNITE-11299 because it
> breaks
> > > SSL
> > > > > on
> > > > > Windows under Java 11.
> > > > >
> > > > > Anything else that needs to be merged before release is branched?
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > чт, 7 мар. 2019 г. в 20:07, Nikolay Izhikov <nizhikov@apache.org>:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > чт, 7 марта 2019 г., 20:00 Denis Magda <dmagda@apache.org>:
> > > > > >
> > > > > > > Igniters,
> > > > > > >
> > > > > > > How about releasing Ignite 2.8 from the master - creating
the
> > > release
> > > > > > > branch on Monday-Tuesday, as fast as we can? Don't want
us to
> > delay
> > > > > with
> > > > > > > Java 11 improvements, they are really helpful from the
> usability
> > > > > > > standpoint.
> > > > > > >
> > > > > > > After this release, let's introduce a practice of maintenance
> > > > releases
> > > > > > > 2.8.x. Those who are working on any improvements and won't
> merge
> > > them
> > > > > to
> > > > > > > the release branch on Monday-Tuesday will be able to roll
out
> in
> > a
> > > > > point
> > > > > > > release like 2.8.1 slightly later.
> > > > > > >
> > > > > > > -
> > > > > > > Denis
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Mar 7, 2019 at 6:22 AM Dmitriy Pavlov <
> > dpavlov@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Ignite Developers,
> > > > > > > >
> > > > > > > > In the separate topic, we've touched the question
of next
> > release
> > > > of
> > > > > > > Apache
> > > > > > > > Ignite.
> > > > > > > >
> > > > > > > > The main reason for the release is Java 11 support,
> modularity
> > > > > changes
> > > > > > > > (actually we have a couple of this kind of fixes).
> > Unfortunately,
> > > > > full
> > > > > > > > modularity support is impossible without 3.0 because
package
> > > > > > refactoring
> > > > > > > is
> > > > > > > > breaking change in some cases.
> > > > > > > >
> > > > > > > > But I clearly remember that in 2.7 thread we've also
> discussed
> > > that
> > > > > the
> > > > > > > > next release will contain step 1 of services redesign,
-
> > > discovery
> > > > > > > protocol
> > > > > > > > usage for services redeploy.
> > > > > > > >
> > > > > > > > We have 2 alternative options for releasing 2.8;
> > > > > > > >
> > > > > > > > A. (in a small way): 2.7-based branch with particular
commits
> > > > > > > cherry-picked
> > > > > > > > into it. It is analog of emergency release but without
really
> > > > > > emergency.
> > > > > > > > Since we don't release our new modules we have more
time to
> > make
> > > it
> > > > > > > modular
> > > > > > > > for 2.9 and make Ignite fully modules compliant in
3.0
> > > > > > > >
> > > > > > > > B. (in large) And, it is a full release based on master,
it
> > will
> > > > > > include
> > > > > > > > new hibernate version, ignite-compress, ignite-services,
and
> > all
> > > > > other
> > > > > > > > changes we have. Once it is published we will not
be able to
> > > change
> > > > > > > > something.
> > > > > > > >
> > > > > > > > Please share your vision, and please stand up if you
want to
> > lead
> > > > > this
> > > > > > > > release (as release manager).
> > > > > > > >
> > > > > > > > Sincerely,
> > > > > > > > Dmitriy Pavlov
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

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