Another topic that I'd like to address before this gets into the final
release. During the voting on RC3 (or even before) we have discussed that
bundling LGPL libs is a bad idea as it really _changes_ the distribution
license for the artifacts. Yet, I see that RC3 is (and perhaps 1.0 will be as
well) including some LGPL and EPL bits (Hibernate is one of the examples).

I think those shouldn't be a part of binaries posted on ASF dist. As an
alternative, anyone providing their own binary archives can do it from their
own servers. It would be a good practice though to warn users of what they are
getting into using the binaries under the aforementioned licenses.

Am I making any sense? Thanks,
  Cos

On Fri, Mar 27, 2015 at 11:13PM, Konstantin Boudnik wrote:
> Guys, to start with:
>  - the format of md5 and sha1 files aren't Unix formats. It suppose to be
> 
> hash    file-name
> 
> e.g.
> 
> % md5sum /etc/hosts
> aa2af9fea577aaedb79056917a6453a9  /etc/hosts
> 
> % sha1sum /etc/hosts
> ee5a6f3e4a3c109114d236c90ca382397fb998fe  /etc/hosts
> 
> When sum-files have this format you can do things like
>     % md5sum -c file-name.md5
> 
> and get your file validated automatically. Let's fix it, please.
> 
> Cos
> 
> On Fri, Mar 27, 2015 at 02:07PM, Dmitriy Setrakyan wrote:
> > I have uploaded the new RC3 release candidate to:
> >   http://people.apache.org/~dsetrakyan/incubator-ignite-1.0.0/
> > 
> > The following changes were made based on all the feedback I got for RC3:
> > 
> > 1. Fixed jdk8.backport wrong license issue.
> > 2. Fixed NOTICE.txt according to comments from IPMC.
> > 3. Fixed LICENSE.txt according to comments from IPMC.
> > 
> > To build a binary release from source run:
> >     mvn clean package -DskipTests
> > 
> > Instructions on how to run RAT and how to build the project are available
> > in DEVNOTES.txt file.
> > 
> > Please start voting.
> > 
> > +1 - to accept Apache Ignite (incubating) 1.0.0
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite (incubating) 1.0.0 (explain why)
> > 
> > D.

Reply via email to