One more: when the binaries are built and ran the version says Ignite ver. 1.0.0-rc3#19691231-sha1:DEV
Instead of 1.0.0 I believe. Although I was building with -P-release, so may be it is a side effect of that. And this error is still there ./bin/ignitevisorcmd.sh Error: Could not find or load main class org.apache.ignite.visor.commands.VisorConsole Which perhaps isn't a blocker for the release Cos On Fri, Mar 13, 2015 at 03:42AM, Konstantin Boudnik wrote: > Checksums are ok > Signature is ok > rat report looks good > sha1sum file looks good, but md5sum still has a weird format. At least now > it is easy to validate, so issue for me. > > -1 however (sorry) because > > - top level directory is called incubator-ignite-ce2230b, should be > incubator-ignite-1.0, I believe. Also, it'd make sense to name the archive > and sum files in the same fashion. This way, once the RC is accepted to the > release all you need to do is to rename the directory but the file names > will remain the same. > > Otherwise, if you rename the diretory inside of the archive, you'll get the > wrong checksums and would need to redo the Vote technically. > > Cos > > On Thu, Mar 12, 2015 at 04:14PM, Dmitriy Setrakyan wrote: > > I have uploaded the new RC3 release candidate to: > > http://people.apache.org/~dsetrakyan/ignite-1.0.0-RC3 > > > > The following changes were made based on all the feedback I got for RC2: > > > > 1. Added DISCLAIMER.txt > > 2. Added DEVNOTES.txt > > 3. Updated NOTICE.txt with section about "org.jdk8.backport" package > > released to public domain under creative commons. > > 4. Removed "licenses" folder > > > > Instructions on how to run RAT and how to build the project are available > > in DEVNOTES.txt file. > > > > Please start voting. > > > > +1 - to accept the RC2 as Apache Ignite (incubating) 1.0 > > 0 - don't care either way > > -1 - DO NOT accept RC2 as Apache Ignite (incubating) 1.0 (explain why)
