Ilya, let me personally thank you for checking and filing this bug. I checked timeline for [result] [vote] email and new email describing new issue. Unfortunately, after closing the vote it is not possible to stop release from publishing (only if RM will delay publish stage after closing the vote). In this case publishing already happened, so replacing existing binary with new one can cause a lot of mess.
What do you think about our future steps to learn from this case? It is possible to keep vote open longer that 72hours if someone is still checking things. Would it help if we agree on RM will delay closing the voting process until all interested participants finish their checks? Sincerely, Dmitriy Pavlov вт, 3 мар. 2020 г. в 20:33, Ilya Kasnacheev <ilya.kasnach...@gmail.com>: > 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 > > > > > > > > > > > > > > > > > > > > > > > >
