As a result: We found that everything is fine and process has not been violated.
On Mon, Jul 31, 2017 at 11:09 PM, Anton Vinogradov <a...@apache.org> wrote: > Cos, > > 1) RC3 and RC4 files are the same because source was not changed from RC3 > to RC4. > RC4 was upload to dev at revision 20551, but RC3 was upload earlier. > These are the two different commits, not a clone. > Also, RC4 was signed by me, but RC3 by Semen. > > 2) > > what was the point of posting rc3 to the dist, instead of rc4 > > We *NEVER* upload RC3 to the release. > > Svn log: > > Added : /release/ignite/2.1.0 (Copy from path: /dev/ignite/2.1.0-*rc4*, > Revision, 20650) > > On Mon, Jul 31, 2017 at 10:44 PM, Konstantin Boudnik <c...@apache.org> > wrote: > >> thanks for checking! >> Technically, speaking we were voting on a different zip-file, that has >> been signed by the release manager. So, I am not sure what was the >> point of posting rc3 to the dist, instead of rc4. Unless of course the >> following statement >> > The artifacts has been upload for RC3 and due to no code changes for >> RC4 they not updated >> was groundless. >> >> You see where I am going with this? >> -- >> With regards, >> Konstantin (Cos) Boudnik >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 >> >> Disclaimer: Opinions expressed in this email are those of the author, >> and do not necessarily represent the views of any company the author >> might be affiliated with at the moment of writing. >> >> >> On Mon, Jul 31, 2017 at 12:21 PM, Anton Vinogradov <a...@apache.org> wrote: >> > Cos, >> > >> > I see that artifacts and checksums are the same: >> > >> > https://dist.apache.org/repos/dist/dev/ignite/?p=20551 >> > >> > RC3: >> > md5 -> 3cd75e1f4e402d8c93b155386afe675c apache-ignite-2.1.0-src.zip >> > (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/ >> apache-ignite-2.1.0-src.zip.md5?p=20551) >> > sha -> b60e95130a6ba758fdf48b8261ac2cd028278f23 >> apache-ignite-2.1.0-src.zip >> > (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/ >> apache-ignite-2.1.0-src.zip.sha1?p=20551) >> > >> > RC4: >> > md5 -> 3cd75e1f4e402d8c93b155386afe675c apache-ignite-2.1.0-src.zip >> > (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc4/ >> apache-ignite-2.1.0-src.zip.md5?p=20551) >> > sha -> b60e95130a6ba758fdf48b8261ac2cd028278f23 >> apache-ignite-2.1.0-src.zip >> > (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc4/ >> apache-ignite-2.1.0-src.zip.sha1?p=20551) >> > >> > >> > Svn log for RC4 -> 2.1.0: >> > >> > Revision: 20651 >> > Author: av >> > Date: 27 июля 2017 г. 18:15:43 >> > Message: >> > Release 2.1.0-rc4 >> > ---- >> > Deleted : /dev/ignite/2.1.0-rc4 >> > Added : /release/ignite/2.1.0 (Copy from path: /dev/ignite/2.1.0-rc4, >> > Revision, 20650) >> > >> > On Mon, Jul 31, 2017 at 8:37 PM, Konstantin Boudnik <c...@apache.org> >> wrote: >> >> >> >> Wait, the artifacts for RC3 were signed differently and had different >> >> checksums than those of RC4. Why the former is now are the official >> >> release artifact if that [VOTE] has been cancelled? >> >> -- >> >> With regards, >> >> Konstantin (Cos) Boudnik >> >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 >> >> >> >> Disclaimer: Opinions expressed in this email are those of the author, >> >> and do not necessarily represent the views of any company the author >> >> might be affiliated with at the moment of writing. >> >> >> >> >> >> On Sat, Jul 29, 2017 at 9:17 AM, Sergey Kozlov <skoz...@gridgain.com> >> >> wrote: >> >> > Denis, that's true. >> >> > >> >> > The artifacts has been upload for RC3 and due to no code changes for >> RC4 >> >> > they not updated >> >> > >> >> > On Sat, Jul 29, 2017 at 5:09 PM, Denis Magda <dma...@gridgain.com> >> >> > wrote: >> >> > >> >> >> I guess that's the JAR's creation time by the build procedure and >> not >> >> >> the >> >> >> uploading time. Looks valid to me. >> >> >> >> >> >> Denis >> >> >> >> >> >> On Saturday, July 29, 2017, 李玉珏@163 <18624049...@163.com> wrote: >> >> >> >> >> >> > Anton, >> >> >> > >> >> >> > >> >> >> > http://repo.maven.apache.org/maven2/org/apache/ignite/ignite >> -core/2.1.0/ >> >> >> > >> >> >> > The timestamp for uploading the artifact is 2017-07-20 17:35, Is >> that >> >> >> > correct? >> >> >> > >> >> >> > >> >> >> > 在 2017/7/28 上午2:06, Anton Vinogradov 写道: >> >> >> > >> >> >> >> Done. >> >> >> >> >> >> >> >> - Maven artifacts released >> >> >> >> - Sources released >> >> >> >> - Site updated >> >> >> >> - Git tag added >> >> >> >> >> >> >> >> On Thu, Jul 27, 2017 at 4:24 PM, Anton Vinogradov <a...@apache.org >> > >> >> >> wrote: >> >> >> >> >> >> >> >> Igniters, >> >> >> >>> >> >> >> >>> Apache Ignite 2.1.0 release (RC4) has been accepted. >> >> >> >>> >> >> >> >>> 7 "+1" votes received: >> >> >> >>> >> >> >> >>> - Valentin Kulichenko (binding) >> >> >> >>> - Nikolai Tikhonov (binding) >> >> >> >>> - Alexey Kuznetsov (binding) >> >> >> >>> - Yakov Zhdanov (binding) >> >> >> >>> - Konstantin Boudnik (binding) >> >> >> >>> - Andrey Gura (binding) >> >> >> >>> - Denis Magda (binding) >> >> >> >>> >> >> >> >>> Vote thread: >> >> >> >>> >> >> >> >>> http://apache-ignite-developers.2346864.n4.nabble. >> >> >> >>> com/VOTE-Apache-Ignite-2-1-0-RC4-td19969.html >> >> >> >>> >> >> >> >>> Ignite 2.1.0 will be released soon. Woohoo! >> >> >> >>> >> >> >> >>> >> >> >> > >> >> >> > >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Sergey Kozlov >> >> > GridGain Systems >> >> > www.gridgain.com >> > >> > >> > >