+1 чт, 7 марта 2019 г., 20:00 Denis Magda <dma...@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 <dpav...@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 > > >
