ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Petr Ivanov <mr.wei...@gmail.com>
Subject Re: Ignite 2.8 Release: Time & Scope & Release manager
Date Thu, 07 Mar 2019 14:26:44 GMT
Can we freeze scope effective immediately, make branch and stabilise whatever should be finished,
producing not emergency but not full regular release?



> On 7 Mar 2019, at 17:21, 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
View raw message