Denis, folks, As it was already mentioned 2.8 is already in maven [1]. Consequently "effectively" released. In my opinion it is not correct to consider release in progress.
Agree that 2.8.1 sounds as a proper option here. [1] https://mvnrepository.com/artifact/org.apache.ignite/ignite-core/2.8.0 Best regards, Ivan Pavlukhin ср, 4 мар. 2020 г. в 17:08, Denis Magda <dma...@apache.org>: > > Dmitriy, > > Ignite 2.8 will be announced as soon as the documentation is prepared and > released. Until then, the release is still considered under progress. Here > is a dedicated discussion for documentation activities. We should be ready > soon: > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-documentation-td46008.html > > Also, I've started a discussion related to our announcement steps. Please > check it out and get involved: > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-announcement-plan-td46238.html > > - > Denis > > > On Wed, Mar 4, 2020 at 6:29 AM Dmitriy Pavlov <dpav...@apache.org> wrote: > > > Hi Folks, > > > > Unfortunately https://dist.apache.org/repos/dist/release/ignite/2.8.0/ is > > already there, so release was happened. I'm not sure it is a good idea to > > substitute binaries later. Was it announced to announce@ ? > > > > IMO, 2.8.1 is ok for that case. > > > > Sincerely, > > Dmitriy Pavlov > > > > ср, 4 мар. 2020 г. в 11:29, Nikolay Izhikov <nizhi...@apache.org>: > > > > > Pavel, ++1. > > > > > > > 4 марта 2020 г., в 11:20, Pavel Tupitsyn <ptupit...@apache.org> > > > написал(а): > > > > > > > > Igniters, > > > > > > > > The release has already happened. > > > > It is on our website [1], it is on Maven [2]. > > > > People are using it, so I don't think we can do anything at this point. > > > > > > > > Bugs happen, we can't delay the release forever because of them. Let's > > > fix > > > > things in 2.8.1. > > > > > > > > [1] https://ignite.apache.org/download.cgi > > > > [2] https://mvnrepository.com/artifact/org.apache.ignite > > > > > > > > > > > > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov <nizhi...@apache.org> > > > wrote: > > > > > > > >> Hello, Igniters. > > > >> > > > >> Do we have a person who can fix this issue in the nearest time? > > > >> Right now IGNITE-12746 is Open and Unassigned. > > > >> > > > >>> 3 марта 2020 г., в 23:54, Denis Magda <dma...@apache.org> > > написал(а): > > > >>> > > > >>> Ilya, > > > >>> > > > >>> Thanks for catching that and sharing. I wonder if there are any other > > > >>> blockers that were pushed to 2.8.x version. If there are a few then > > we > > > >> can > > > >>> produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix > > the > > > >>> issue with putAll, update the binaries and finish the process. > > > >>> > > > >>> - > > > >>> Denis > > > >>> > > > >>> > > > >>> On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev < > > > >> ilya.kasnach...@gmail.com> > > > >>> wrote: > > > >>> > > > >>>> Hello! > > > >>>> > > > >>>> I have filed an issue > > > >> https://issues.apache.org/jira/browse/IGNITE-12746 > > > >>>> > > > >>>> I think this is potentially a game breaker and makes me recommend > > > >> avoiding > > > >>>> 2.8, if we release it without fix (for now). > > > >>>> > > > >>>> If you are using any partitioned caches, anyway. > > > >>>> > > > >>>> So I suggest we withhold 2.8. > > > >>>> > > > >>>> Regards, > > > >>>> -- > > > >>>> Ilya Kasnacheev > > > >>>> > > > >>>> > > > >>>> вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov <mmu...@apache.org>: > > > >>>> > > > >>>>> Ilya, > > > >>>>> > > > >>>>> I do not want to force the release no matter what happens, but I > > > think > > > >>>>> we should release what we have to get feedback not just from the > > > >>>>> developer community but from our users too. > > > >>>>> > > > >>>>> And fix all these issues in 2.8.1. > > > >>>>> > > > >>>>> On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev < > > > >> ilya.kasnach...@gmail.com> > > > >>>>> wrote: > > > >>>>>> > > > >>>>>> Hello! > > > >>>>>> > > > >>>>>> Can we please hold back publishing AI-2.8.0-rc1 as public Apache > > > >> Ignite > > > >>>>> 2.8 > > > >>>>>> release? > > > >>>>>> > > > >>>>>> I have just been notified that > > > >>>>>> > > > >>>>> > > > >>>> > > > >> > > > > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated > > > >>>>>> > > > >>>>> > > > >>>> > > > >> > > > > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed > > > >>>>>> are flaky: they seem to deadlock on putAll sorted keys maps. They > > > used > > > >>>> to > > > >>>>>> pass solidly on 2.7, but fail on master and ignite-2.8. > > > >>>>>> > > > >>>>>> (They fail around 1 time out of 10, so just run them 25 times to > > > >> check) > > > >>>>>> > > > >>>>>> If there is indeed a deadlock, this would become a blocker to this > > > >>>>> release, > > > >>>>>> in my opinion, but I need some time to check. > > > >>>>>> > > > >>>>>> Regards, > > > >>>>>> -- > > > >>>>>> Ilya Kasnacheev > > > >>>>>> > > > >>>>>> > > > >>>>>> вс, 1 мар. 2020 г. в 11:29, Maxim Muzafarov <mmu...@apache.org>: > > > >>>>>> > > > >>>>>>> Ivan, > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> I agree with you that the more members will check the release the > > > >>>>>>> better will be. That's why I've shared the release candidate > > links > > > >>>> [1] > > > >>>>>>> before starting a vote. The best time for starting a vote is not > > > >>>>>>> mentioned at our release wiki page [2] (should we?) and I've also > > > >>>>>>> failed with googling the best practices for it too. So, I've > > > supposed > > > >>>>>>> since all of us are working on their own tasks during weekdays > > the > > > >>>>>>> free time on the weekend is the best choice for cheking\voting on > > > the > > > >>>>>>> release. Probably this decision was wrong. > > > >>>>>>> > > > >>>>>>> [1] > > > >>>>>>> > > > >>>>> > > > >>>> > > > >> > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-tp43616p46117.html > > > >>>>>>> [2] > > > >>>> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > > >>>>>>> > > > >>>>>>> On Sun, 1 Mar 2020 at 00:37, Ivan Pavlukhin <vololo...@gmail.com > > > > > > >>>>> wrote: > > > >>>>>>>> > > > >>>>>>>> Also I have a comment regarding to voting. Voting for 72 hour > > > >>>>> spanning > > > >>>>>>>> a weekend sounds a little bit odd to me. In a particular case > > the > > > >>>>> more > > > >>>>>>>> people check the release the better. And I suppose there is more > > > >>>> time > > > >>>>>>>> for it on weekdays for the majority. > > > >>>>>>>> > > > >>>>>>>> Best regards, > > > >>>>>>>> Ivan Pavlukhin > > > >>>>>>>> > > > >>>>>>>> вс, 1 мар. 2020 г. в 00:33, Ivan Pavlukhin <vololo...@gmail.com > > >: > > > >>>>>>>>> > > > >>>>>>>>>> As I remember, that Pavlov suggested to discuss threats on a > > > >>>>> private > > > >>>>>>> PMC list > > > >>>>>>>>> Cannot understand why it should be discussed on a private list. > > > >>>>> What > > > >>>>>>>>> is the clue? > > > >>>>>>>>> > > > >>>>>>>>> Best regards, > > > >>>>>>>>> Ivan Pavlukhin > > > >>>>>>>>> > > > >>>>>>>>> сб, 29 февр. 2020 г. в 16:00, Alexey Zinoviev < > > > >>>>> zaleslaw....@gmail.com > > > >>>>>>>> : > > > >>>>>>>>>> > > > >>>>>>>>>> As I remember, that Pavlov suggested to discuss threats on a > > > >>>>> private > > > >>>>>>> PMC > > > >>>>>>>>>> list > > > >>>>>>>>>> > > > >>>>>>>>>> сб, 29 февр. 2020 г., 15:12 Ilya Kasnacheev < > > > >>>>>>> ilya.kasnach...@gmail.com>: > > > >>>>>>>>>> > > > >>>>>>>>>>> Hello! > > > >>>>>>>>>>> > > > >>>>>>>>>>> As far as my understanding goes, ignite-zookeeper is listed > > > >>>> for > > > >>>>>>> removal > > > >>>>>>>>>>> because it brings a lot of dependencies, some of which may > > > >>>> have > > > >>>>>>> known > > > >>>>>>>>>>> vulnerabilities, which will make the distribution also > > > >>>>> considered > > > >>>>>>>>>>> vulnerable by some scanners. > > > >>>>>>>>>>> > > > >>>>>>>>>>> Regards, > > > >>>>>>>>>>> -- > > > >>>>>>>>>>> Ilya Kasnacheev > > > >>>>>>>>>>> > > > >>>>>>>>>>> > > > >>>>>>>>>>> сб, 29 февр. 2020 г. в 14:18, Alexey Zinoviev < > > > >>>>>>> zaleslaw....@gmail.com>: > > > >>>>>>>>>>> > > > >>>>>>>>>>>> Ok, lets move to this thread. Also, the slim release could > > > >>>> be > > > >>>>>>> form by > > > >>>>>>>>>>>> voting on user-list > > > >>>>>>>>>>>> > > > >>>>>>>>>>>> сб, 29 февр. 2020 г., 9:55 Alexey Goncharuk < > > > >>>>>>> alexey.goncha...@gmail.com > > > >>>>>>>>>>>> : > > > >>>>>>>>>>>> > > > >>>>>>>>>>>>> Nikolay, Alexey, > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>>> First, the idea of the slim binary release and docker > > > >>>>> image was > > > >>>>>>>>>>> discussed > > > >>>>>>>>>>>>> openly on the dev-list [1]. Second, nobody talks about > > > >>>>>>> removing these > > > >>>>>>>>>>>>> modules from the product. The idea was to create an > > > >>>>> additional > > > >>>>>>>>>>>> distribution > > > >>>>>>>>>>>>> which is much lighter than the current full package to > > > >>>>> reduce > > > >>>>>>> the size > > > >>>>>>>>>>> of > > > >>>>>>>>>>>>> the downloadable artifact and reduce the number of > > > >>>>> potential > > > >>>>>>>>>>>>> vulnerabilities in third-party libraries. > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>>> The list of modules was chosen subjectively by the number > > > >>>>> of > > > >>>>>>> questions > > > >>>>>>>>>>> on > > > >>>>>>>>>>>>> the user-list, number third-party libraries (size) and > > > >>>>>>> vulnerabilities > > > >>>>>>>>>>>> the > > > >>>>>>>>>>>>> module brings. Given that there are still questions, we > > > >>>> are > > > >>>>>>> definitely > > > >>>>>>>>>>>> not > > > >>>>>>>>>>>>> ready to release it in 2.8.0. > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>>> Let's move discussion to the original thread? > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>>> [1] > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>> > > > >>>>>>>>>>> > > > >>>>>>> > > > >>>>> > > > >>>> > > > >> > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Slim-binary-release-and-docker-image-for-Apache-Ignite-td45110.html > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>> > > > >>>>>>>>>>> > > > >>>>>>> > > > >>>>> > > > >>>> > > > >> > > > >> > > > > > > > >
