[ANNOUNCE] Apache Ignite 2.4.0 Released: Machine Learning GA and Spark DataFrames

[dmagda]

Usually, Ignite community rolls out a new version once in 3 months, but we
had to make an exception for Apache Ignite 2.4 that consumed five months in
total.

We could easily blame Thanksgiving, Christmas and New Year holidays for the
delay and would be forgiven, but, in fact, we were forging the release you
can't just pass by.

Let's dive in and look for a big fish:
https://blogs.apache.org/ignite/entry/apache-ignite-2-4-brings

The full list of the changes can be found here:
https://ignite.apache.org/releases/2.4.0/release_notes.html

Ready to try then navigate to our downloads page:
https://ignite.apache.org/download.cgi

--
Denis

[dmagda]

Igniters,

Please use your social media accounts to promote the release we were
working on for a while:
https://twitter.com/denismagda/status/974438862465351681

It will be great if you can translate the article into your native language
and publish it in your country of origin.

<https://twitter.com/denismagda/status/974438862465351681>--
Denis

---------- Forwarded message ----------
From: Denis Magda <[hidden email]>
Date: Thu, Mar 15, 2018 at 5:09 PM
Subject: [ANNOUNCE] Apache Ignite 2.4.0 Released: Machine Learning GA and
Spark DataFrames
To: [hidden email], [hidden email], [hidden email]


Usually, Ignite community rolls out a new version once in 3 months, but we
had to make an exception for Apache Ignite 2.4 that consumed five months in
total.

We could easily blame Thanksgiving, Christmas and New Year holidays for the
delay and would be forgiven, but, in fact, we were forging the release you
can't just pass by.

Let's dive in and look for a big fish: https://blogs.apache.
org/ignite/entry/apache-ignite-2-4-brings

The full list of the changes can be found here: https://ignite.apache.org/
releases/2.4.0/release_notes.html

Ready to try then navigate to our downloads page:
https://ignite.apache.org/download.cgi

--
Denis

[sebb]

What is the project about? Why should I be interested in it?
[rhetorical questions]

The Announce emails are sent to people not on the developer or user lists.
Most will have no idea what the project is about.

So the e-mails should contain at least brief details of what the
product does, and some info on why the new release might be of
interest to them.

Readers should not have to click the link to find out the basic information
(although of course it is useful to have such links for further detail).

Please can you add that information to future announce mails?

Thanks.


On 16 March 2018 at 00:09, Denis Magda <[hidden email]> wrote:

> Usually, Ignite community rolls out a new version once in 3 months, but we
> had to make an exception for Apache Ignite 2.4 that consumed five months in
> total.
>
> We could easily blame Thanksgiving, Christmas and New Year holidays for the
> delay and would be forgiven, but, in fact, we were forging the release you
> can't just pass by.
>
> Let's dive in and look for a big fish:
> https://blogs.apache.org/ignite/entry/apache-ignite-2-4-brings
>
> The full list of the changes can be found here:
> https://ignite.apache.org/releases/2.4.0/release_notes.html
>
> Ready to try then navigate to our downloads page:
> https://ignite.apache.org/download.cgi
>
> --
> Denis

[dmagda]

All our previous announcements were formatted precisely the way you
suggest. However, I haven't fount that template effective. Personally, I
archive an email immediately if see it's written the standard way and I
know nothing about the product.

That's why I decided to experiment targeting those who already know Ignite
and interested in solutions it provided in 2.4. Really appreciate your
feedback and will see how to incorporate your suggestions for future
announcements. Just don't like to see emails written by "robots".

--
Denis



On Fri, Mar 16, 2018 at 8:34 AM, sebb <[hidden email]> wrote:

> What is the project about? Why should I be interested in it?
> [rhetorical questions]
>
> The Announce emails are sent to people not on the developer or user lists.
> Most will have no idea what the project is about.
>
> So the e-mails should contain at least brief details of what the
> product does, and some info on why the new release might be of
> interest to them.
>
> Readers should not have to click the link to find out the basic information
> (although of course it is useful to have such links for further detail).
>
> Please can you add that information to future announce mails?
>
> Thanks.
>
>
> On 16 March 2018 at 00:09, Denis Magda <[hidden email]> wrote:
> > Usually, Ignite community rolls out a new version once in 3 months, but
> we
> > had to make an exception for Apache Ignite 2.4 that consumed five months
> in
> > total.
> >
> > We could easily blame Thanksgiving, Christmas and New Year holidays for
> the
> > delay and would be forgiven, but, in fact, we were forging the release
> you
> > can't just pass by.
> >
> > Let's dive in and look for a big fish:
> > https://blogs.apache.org/ignite/entry/apache-ignite-2-4-brings
> >
> > The full list of the changes can be found here:
> > https://ignite.apache.org/releases/2.4.0/release_notes.html
> >
> > Ready to try then navigate to our downloads page:
> > https://ignite.apache.org/download.cgi
> >
> > --
> > Denis
>

[sebb]

Perhaps have a look at the announce mails sent by Httpd and Tomcat.

Even though these projects are better known than most, they still
provide a short summary of what they do.
I don't think they read as though written by robots...

On 16 March 2018 at 17:02, Denis Magda <[hidden email]> wrote:

> All our previous announcements were formatted precisely the way you suggest.
> However, I haven't fount that template effective. Personally, I archive an
> email immediately if see it's written the standard way and I know nothing
> about the product.
>
> That's why I decided to experiment targeting those who already know Ignite
> and interested in solutions it provided in 2.4. Really appreciate your
> feedback and will see how to incorporate your suggestions for future
> announcements. Just don't like to see emails written by "robots".
>
> --
> Denis
>
>
>
> On Fri, Mar 16, 2018 at 8:34 AM, sebb <[hidden email]> wrote:
>>
>> What is the project about? Why should I be interested in it?
>> [rhetorical questions]
>>
>> The Announce emails are sent to people not on the developer or user lists.
>> Most will have no idea what the project is about.
>>
>> So the e-mails should contain at least brief details of what the
>> product does, and some info on why the new release might be of
>> interest to them.
>>
>> Readers should not have to click the link to find out the basic
>> information
>> (although of course it is useful to have such links for further detail).
>>
>> Please can you add that information to future announce mails?
>>
>> Thanks.
>>
>>
>> On 16 March 2018 at 00:09, Denis Magda <[hidden email]> wrote:
>> > Usually, Ignite community rolls out a new version once in 3 months, but
>> > we
>> > had to make an exception for Apache Ignite 2.4 that consumed five months
>> > in
>> > total.
>> >
>> > We could easily blame Thanksgiving, Christmas and New Year holidays for
>> > the
>> > delay and would be forgiven, but, in fact, we were forging the release
>> > you
>> > can't just pass by.
>> >
>> > Let's dive in and look for a big fish:
>> > https://blogs.apache.org/ignite/entry/apache-ignite-2-4-brings
>> >
>> > The full list of the changes can be found here:
>> > https://ignite.apache.org/releases/2.4.0/release_notes.html
>> >
>> > Ready to try then navigate to our downloads page:
>> > https://ignite.apache.org/download.cgi
>> >
>> > --
>> > Denis
>
>

[dmagda]

Thanks for the pointers, will check them up.

Have a good weekend,
Denis

On Fri, Mar 16, 2018 at 11:16 AM, sebb <[hidden email]> wrote:

> Perhaps have a look at the announce mails sent by Httpd and Tomcat.
>
> Even though these projects are better known than most, they still
> provide a short summary of what they do.
> I don't think they read as though written by robots...
>
> On 16 March 2018 at 17:02, Denis Magda <[hidden email]> wrote:
> > All our previous announcements were formatted precisely the way you
> suggest.
> > However, I haven't fount that template effective. Personally, I archive
> an
> > email immediately if see it's written the standard way and I know nothing
> > about the product.
> >
> > That's why I decided to experiment targeting those who already know
> Ignite
> > and interested in solutions it provided in 2.4. Really appreciate your
> > feedback and will see how to incorporate your suggestions for future
> > announcements. Just don't like to see emails written by "robots".
> >
> > --
> > Denis
> >
> >
> >
> > On Fri, Mar 16, 2018 at 8:34 AM, sebb <[hidden email]> wrote:
> >>
> >> What is the project about? Why should I be interested in it?
> >> [rhetorical questions]
> >>
> >> The Announce emails are sent to people not on the developer or user
> lists.
> >> Most will have no idea what the project is about.
> >>
> >> So the e-mails should contain at least brief details of what the
> >> product does, and some info on why the new release might be of
> >> interest to them.
> >>
> >> Readers should not have to click the link to find out the basic
> >> information
> >> (although of course it is useful to have such links for further detail).
> >>
> >> Please can you add that information to future announce mails?
> >>
> >> Thanks.
> >>
> >>
> >> On 16 March 2018 at 00:09, Denis Magda <[hidden email]> wrote:
> >> > Usually, Ignite community rolls out a new version once in 3 months,
> but
> >> > we
> >> > had to make an exception for Apache Ignite 2.4 that consumed five
> months
> >> > in
> >> > total.
> >> >
> >> > We could easily blame Thanksgiving, Christmas and New Year holidays
> for
> >> > the
> >> > delay and would be forgiven, but, in fact, we were forging the release
> >> > you
> >> > can't just pass by.
> >> >
> >> > Let's dive in and look for a big fish:
> >> > https://blogs.apache.org/ignite/entry/apache-ignite-2-4-brings
> >> >
> >> > The full list of the changes can be found here:
> >> > https://ignite.apache.org/releases/2.4.0/release_notes.html
> >> >
> >> > Ready to try then navigate to our downloads page:
> >> > https://ignite.apache.org/download.cgi
> >> >
> >> > --
> >> > Denis
> >
> >
>

[dsetrakyan]

 Denis,

The brief pitch we provide on the home page should be good enough, no?

Apache Ignite™ is a memory-centric distributed database, caching, and
> processing platform for
> transactional, analytical, and streaming workloads, delivering in-memory
> speeds at petabyte scale


D.



On Fri, Mar 16, 2018 at 11:19 AM, Denis Magda <[hidden email]> wrote:

> Thanks for the pointers, will check them up.
>
> Have a good weekend,
> Denis
>
> On Fri, Mar 16, 2018 at 11:16 AM, sebb <[hidden email]> wrote:
>
> > Perhaps have a look at the announce mails sent by Httpd and Tomcat.
> >
> > Even though these projects are better known than most, they still
> > provide a short summary of what they do.
> > I don't think they read as though written by robots...
> >
> > On 16 March 2018 at 17:02, Denis Magda <[hidden email]> wrote:
> > > All our previous announcements were formatted precisely the way you
> > suggest.
> > > However, I haven't fount that template effective. Personally, I archive
> > an
> > > email immediately if see it's written the standard way and I know
> nothing
> > > about the product.
> > >
> > > That's why I decided to experiment targeting those who already know
> > Ignite
> > > and interested in solutions it provided in 2.4. Really appreciate your
> > > feedback and will see how to incorporate your suggestions for future
> > > announcements. Just don't like to see emails written by "robots".
> > >
> > > --
> > > Denis
> > >
> > >
> > >
> > > On Fri, Mar 16, 2018 at 8:34 AM, sebb <[hidden email]> wrote:
> > >>
> > >> What is the project about? Why should I be interested in it?
> > >> [rhetorical questions]
> > >>
> > >> The Announce emails are sent to people not on the developer or user
> > lists.
> > >> Most will have no idea what the project is about.
> > >>
> > >> So the e-mails should contain at least brief details of what the
> > >> product does, and some info on why the new release might be of
> > >> interest to them.
> > >>
> > >> Readers should not have to click the link to find out the basic
> > >> information
> > >> (although of course it is useful to have such links for further
> detail).
> > >>
> > >> Please can you add that information to future announce mails?
> > >>
> > >> Thanks.
> > >>
> > >>
> > >> On 16 March 2018 at 00:09, Denis Magda <[hidden email]> wrote:
> > >> > Usually, Ignite community rolls out a new version once in 3 months,
> > but
> > >> > we
> > >> > had to make an exception for Apache Ignite 2.4 that consumed five
> > months
> > >> > in
> > >> > total.
> > >> >
> > >> > We could easily blame Thanksgiving, Christmas and New Year holidays
> > for
> > >> > the
> > >> > delay and would be forgiven, but, in fact, we were forging the
> release
> > >> > you
> > >> > can't just pass by.
> > >> >
> > >> > Let's dive in and look for a big fish:
> > >> > https://blogs.apache.org/ignite/entry/apache-ignite-2-4-brings
> > >> >
> > >> > The full list of the changes can be found here:
> > >> > https://ignite.apache.org/releases/2.4.0/release_notes.html
> > >> >
> > >> > Ready to try then navigate to our downloads page:
> > >> > https://ignite.apache.org/download.cgi
> > >> >
> > >> > --
> > >> > Denis
> > >
> > >
> >
>

[dmagda]

Absolutely. The concern here was that I didn't provide the necessary
description in general.

--
Denis

On Fri, Mar 16, 2018 at 3:51 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

>  Denis,
>
> The brief pitch we provide on the home page should be good enough, no?
>
> Apache Ignite™ is a memory-centric distributed database, caching, and
> > processing platform for
> > transactional, analytical, and streaming workloads, delivering in-memory
> > speeds at petabyte scale
>
>
> D.
>
>
>
> On Fri, Mar 16, 2018 at 11:19 AM, Denis Magda <[hidden email]> wrote:
>
> > Thanks for the pointers, will check them up.
> >
> > Have a good weekend,
> > Denis
> >
> > On Fri, Mar 16, 2018 at 11:16 AM, sebb <[hidden email]> wrote:
> >
> > > Perhaps have a look at the announce mails sent by Httpd and Tomcat.
> > >
> > > Even though these projects are better known than most, they still
> > > provide a short summary of what they do.
> > > I don't think they read as though written by robots...
> > >
> > > On 16 March 2018 at 17:02, Denis Magda <[hidden email]> wrote:
> > > > All our previous announcements were formatted precisely the way you
> > > suggest.
> > > > However, I haven't fount that template effective. Personally, I
> archive
> > > an
> > > > email immediately if see it's written the standard way and I know
> > nothing
> > > > about the product.
> > > >
> > > > That's why I decided to experiment targeting those who already know
> > > Ignite
> > > > and interested in solutions it provided in 2.4. Really appreciate
> your
> > > > feedback and will see how to incorporate your suggestions for future
> > > > announcements. Just don't like to see emails written by "robots".
> > > >
> > > > --
> > > > Denis
> > > >
> > > >
> > > >
> > > > On Fri, Mar 16, 2018 at 8:34 AM, sebb <[hidden email]> wrote:
> > > >>
> > > >> What is the project about? Why should I be interested in it?
> > > >> [rhetorical questions]
> > > >>
> > > >> The Announce emails are sent to people not on the developer or user
> > > lists.
> > > >> Most will have no idea what the project is about.
> > > >>
> > > >> So the e-mails should contain at least brief details of what the
> > > >> product does, and some info on why the new release might be of
> > > >> interest to them.
> > > >>
> > > >> Readers should not have to click the link to find out the basic
> > > >> information
> > > >> (although of course it is useful to have such links for further
> > detail).
> > > >>
> > > >> Please can you add that information to future announce mails?
> > > >>
> > > >> Thanks.
> > > >>
> > > >>
> > > >> On 16 March 2018 at 00:09, Denis Magda <[hidden email]> wrote:
> > > >> > Usually, Ignite community rolls out a new version once in 3
> months,
> > > but
> > > >> > we
> > > >> > had to make an exception for Apache Ignite 2.4 that consumed five
> > > months
> > > >> > in
> > > >> > total.
> > > >> >
> > > >> > We could easily blame Thanksgiving, Christmas and New Year
> holidays
> > > for
> > > >> > the
> > > >> > delay and would be forgiven, but, in fact, we were forging the
> > release
> > > >> > you
> > > >> > can't just pass by.
> > > >> >
> > > >> > Let's dive in and look for a big fish:
> > > >> > https://blogs.apache.org/ignite/entry/apache-ignite-2-4-brings
> > > >> >
> > > >> > The full list of the changes can be found here:
> > > >> > https://ignite.apache.org/releases/2.4.0/release_notes.html
> > > >> >
> > > >> > Ready to try then navigate to our downloads page:
> > > >> > https://ignite.apache.org/download.cgi
> > > >> >
> > > >> > --
> > > >> > Denis
> > > >
> > > >
> > >
> >
>

[sebb]

Yes, that would be ideal for the announce emails.

On 16 March 2018 at 23:42, Denis Magda <[hidden email]> wrote:

> Absolutely. The concern here was that I didn't provide the necessary
> description in general.
>
> --
> Denis
>
> On Fri, Mar 16, 2018 at 3:51 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>>
>>  Denis,
>>
>> The brief pitch we provide on the home page should be good enough, no?
>>
>> Apache Ignite™ is a memory-centric distributed database, caching, and
>> > processing platform for
>> > transactional, analytical, and streaming workloads, delivering in-memory
>> > speeds at petabyte scale
>>
>>
>> D.
>>
>>
>>
>> On Fri, Mar 16, 2018 at 11:19 AM, Denis Magda <[hidden email]> wrote:
>>
>> > Thanks for the pointers, will check them up.
>> >
>> > Have a good weekend,
>> > Denis
>> >
>> > On Fri, Mar 16, 2018 at 11:16 AM, sebb <[hidden email]> wrote:
>> >
>> > > Perhaps have a look at the announce mails sent by Httpd and Tomcat.
>> > >
>> > > Even though these projects are better known than most, they still
>> > > provide a short summary of what they do.
>> > > I don't think they read as though written by robots...
>> > >
>> > > On 16 March 2018 at 17:02, Denis Magda <[hidden email]> wrote:
>> > > > All our previous announcements were formatted precisely the way you
>> > > suggest.
>> > > > However, I haven't fount that template effective. Personally, I
>> > > > archive
>> > > an
>> > > > email immediately if see it's written the standard way and I know
>> > nothing
>> > > > about the product.
>> > > >
>> > > > That's why I decided to experiment targeting those who already know
>> > > Ignite
>> > > > and interested in solutions it provided in 2.4. Really appreciate
>> > > > your
>> > > > feedback and will see how to incorporate your suggestions for future
>> > > > announcements. Just don't like to see emails written by "robots".
>> > > >
>> > > > --
>> > > > Denis
>> > > >
>> > > >
>> > > >
>> > > > On Fri, Mar 16, 2018 at 8:34 AM, sebb <[hidden email]> wrote:
>> > > >>
>> > > >> What is the project about? Why should I be interested in it?
>> > > >> [rhetorical questions]
>> > > >>
>> > > >> The Announce emails are sent to people not on the developer or user
>> > > lists.
>> > > >> Most will have no idea what the project is about.
>> > > >>
>> > > >> So the e-mails should contain at least brief details of what the
>> > > >> product does, and some info on why the new release might be of
>> > > >> interest to them.
>> > > >>
>> > > >> Readers should not have to click the link to find out the basic
>> > > >> information
>> > > >> (although of course it is useful to have such links for further
>> > detail).
>> > > >>
>> > > >> Please can you add that information to future announce mails?
>> > > >>
>> > > >> Thanks.
>> > > >>
>> > > >>
>> > > >> On 16 March 2018 at 00:09, Denis Magda <[hidden email]> wrote:
>> > > >> > Usually, Ignite community rolls out a new version once in 3
>> > > >> > months,
>> > > but
>> > > >> > we
>> > > >> > had to make an exception for Apache Ignite 2.4 that consumed five
>> > > months
>> > > >> > in
>> > > >> > total.
>> > > >> >
>> > > >> > We could easily blame Thanksgiving, Christmas and New Year
>> > > >> > holidays
>> > > for
>> > > >> > the
>> > > >> > delay and would be forgiven, but, in fact, we were forging the
>> > release
>> > > >> > you
>> > > >> > can't just pass by.
>> > > >> >
>> > > >> > Let's dive in and look for a big fish:
>> > > >> > https://blogs.apache.org/ignite/entry/apache-ignite-2-4-brings
>> > > >> >
>> > > >> > The full list of the changes can be found here:
>> > > >> > https://ignite.apache.org/releases/2.4.0/release_notes.html
>> > > >> >
>> > > >> > Ready to try then navigate to our downloads page:
>> > > >> > https://ignite.apache.org/download.cgi
>> > > >> >
>> > > >> > --
>> > > >> > Denis
>> > > >
>> > > >
>> > >
>> >
>
>