ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Ignite 2.8 Release: Time & Scope & Release manager
Date Thu, 07 Mar 2019 18:02:13 GMT
Dmitry,

“Master is always releasable” is a myth, let’s do not be naive. We develop
complex product. Many features are being developed in iterations. Many
features are developed by different contributors and have to be aligned
with each other after merge. And in the end all this should be tested and
benchmarked before becoming a product.

None serious products are “releasable” from master in a classical “release”
sense. Nightly builds are not releases.

чт, 7 марта 2019 г. в 20:31, Dmitriy Pavlov <dpavlov@apache.org>:

> Vova it is not cool I have to remind Ignite veterans about How to
> contribute page, it says the master is release ready branch.
>
> Otherwise feature is developed in its own branch.
>
> So my vote goes for master-based release.
>
> чт, 7 мар. 2019 г. в 20:28, Vladimir Ozerov <vozerov@gridgain.com>:
>
> > 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