Ignite 1.7 RELEASE_NOTES

[Pavel Tupitsyn]

Igniters,

RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me. There
are likely more noteworthy changes since 1.6.

Let's discuss the changes to be included in release notes and fix them.

Please reply to this email with your proposals.

Pavel.

[Pavel Tupitsyn]

Noteworthy .NET changes:

* User-defined AffinityFunction
* ASP.NET Output Cache provider
* .NET configuration in Apache.Ignite.exe
* Distributed joins in SQL and LINQ
* Forward Java output to the .NET console
* Add Java stack trace on .NET side in IgniteException.InnerException
* Move examples from Spring XML to app.config
* Configuration schema NuGet package
* Fix compute jobs executing on client nodes
* Fix self-joins in LINQ


On Mon, Aug 1, 2016 at 1:43 PM, Pavel Tupitsyn <[hidden email]> wrote:

> Igniters,
>
> RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me. There
> are likely more noteworthy changes since 1.6.
>
> Let's discuss the changes to be included in release notes and fix them.
>
> Please reply to this email with your proposals.
>
> Pavel.
>

[Igor Sapego]

C++ features:
* Added support for distributed joins in SqlQuery and SqlFieldsQuery.
* Serialization and deserialization performance improved.

ODBC features:
* Added support for the numeric type (SQL_NUMERIC_STRUCT).

Best Regards,
Igor

On Mon, Aug 1, 2016 at 1:59 PM, Pavel Tupitsyn <[hidden email]> wrote:

> Noteworthy .NET changes:
>
> * User-defined AffinityFunction
> * ASP.NET Output Cache provider
> * .NET configuration in Apache.Ignite.exe
> * Distributed joins in SQL and LINQ
> * Forward Java output to the .NET console
> * Add Java stack trace on .NET side in IgniteException.InnerException
> * Move examples from Spring XML to app.config
> * Configuration schema NuGet package
> * Fix compute jobs executing on client nodes
> * Fix self-joins in LINQ
>
>
> On Mon, Aug 1, 2016 at 1:43 PM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Igniters,
> >
> > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me.
> There
> > are likely more noteworthy changes since 1.6.
> >
> > Let's discuss the changes to be included in release notes and fix them.
> >
> > Please reply to this email with your proposals.
> >
> > Pavel.
> >
>

[Vladimir Ozerov]

Folks,

I updated release notes a bit. Please review my changes.

Vladimir.

On Mon, Aug 1, 2016 at 2:17 PM, Igor Sapego <[hidden email]> wrote:

> C++ features:
> * Added support for distributed joins in SqlQuery and SqlFieldsQuery.
> * Serialization and deserialization performance improved.
>
> ODBC features:
> * Added support for the numeric type (SQL_NUMERIC_STRUCT).
>
> Best Regards,
> Igor
>
> On Mon, Aug 1, 2016 at 1:59 PM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Noteworthy .NET changes:
> >
> > * User-defined AffinityFunction
> > * ASP.NET Output Cache provider
> > * .NET configuration in Apache.Ignite.exe
> > * Distributed joins in SQL and LINQ
> > * Forward Java output to the .NET console
> > * Add Java stack trace on .NET side in IgniteException.InnerException
> > * Move examples from Spring XML to app.config
> > * Configuration schema NuGet package
> > * Fix compute jobs executing on client nodes
> > * Fix self-joins in LINQ
> >
> >
> > On Mon, Aug 1, 2016 at 1:43 PM, Pavel Tupitsyn <[hidden email]>
> > wrote:
> >
> > > Igniters,
> > >
> > > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me.
> > There
> > > are likely more noteworthy changes since 1.6.
> > >
> > > Let's discuss the changes to be included in release notes and fix them.
> > >
> > > Please reply to this email with your proposals.
> > >
> > > Pavel.
> > >
> >
>

[Pavel Tupitsyn]

Thanks Vladimir, .NET part looks ok to me.

On Mon, Aug 1, 2016 at 2:36 PM, Vladimir Ozerov <[hidden email]>
wrote:

> Folks,
>
> I updated release notes a bit. Please review my changes.
>
> Vladimir.
>
> On Mon, Aug 1, 2016 at 2:17 PM, Igor Sapego <[hidden email]> wrote:
>
> > C++ features:
> > * Added support for distributed joins in SqlQuery and SqlFieldsQuery.
> > * Serialization and deserialization performance improved.
> >
> > ODBC features:
> > * Added support for the numeric type (SQL_NUMERIC_STRUCT).
> >
> > Best Regards,
> > Igor
> >
> > On Mon, Aug 1, 2016 at 1:59 PM, Pavel Tupitsyn <[hidden email]>
> > wrote:
> >
> > > Noteworthy .NET changes:
> > >
> > > * User-defined AffinityFunction
> > > * ASP.NET Output Cache provider
> > > * .NET configuration in Apache.Ignite.exe
> > > * Distributed joins in SQL and LINQ
> > > * Forward Java output to the .NET console
> > > * Add Java stack trace on .NET side in IgniteException.InnerException
> > > * Move examples from Spring XML to app.config
> > > * Configuration schema NuGet package
> > > * Fix compute jobs executing on client nodes
> > > * Fix self-joins in LINQ
> > >
> > >
> > > On Mon, Aug 1, 2016 at 1:43 PM, Pavel Tupitsyn <[hidden email]>
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me.
> > > There
> > > > are likely more noteworthy changes since 1.6.
> > > >
> > > > Let's discuss the changes to be included in release notes and fix
> them.
> > > >
> > > > Please reply to this email with your proposals.
> > > >
> > > > Pavel.
> > > >
> > >
> >
>

[Konstantin Boudnik-2]

Tracking the "Fixed in release" on the JIRA tickets would take care about any
gaps pretty much automatically. In general it's a good idea for an RM to run a
spring-cleaning on the JIRA tickets to scope up the release. Then once all
tickets are fixed, you can simply _generate_ the release notes with a
single-button click.

Cos

On Mon, Aug 01, 2016 at 01:43PM, Pavel Tupitsyn wrote:

> Igniters,
>
> RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me. There
> are likely more noteworthy changes since 1.6.
>
> Let's discuss the changes to be included in release notes and fix them.
>
> Please reply to this email with your proposals.
>
> Pavel.

[Pavel Tupitsyn]

Cos, we track versions in JIRA. There are 230 closed issues for 1.7:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
We can't just dump all of them to release notes.

On Tue, Aug 2, 2016 at 10:31 PM, Konstantin Boudnik <[hidden email]> wrote:

> Tracking the "Fixed in release" on the JIRA tickets would take care about
> any
> gaps pretty much automatically. In general it's a good idea for an RM to
> run a
> spring-cleaning on the JIRA tickets to scope up the release. Then once all
> tickets are fixed, you can simply _generate_ the release notes with a
> single-button click.
>
> Cos
>
> On Mon, Aug 01, 2016 at 01:43PM, Pavel Tupitsyn wrote:
> > Igniters,
> >
> > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me.
> There
> > are likely more noteworthy changes since 1.6.
> >
> > Let's discuss the changes to be included in release notes and fix them.
> >
> > Please reply to this email with your proposals.
> >
> > Pavel.
>

[Konstantin Boudnik-2]

On Wed, Aug 03, 2016 at 10:47AM, Pavel Tupitsyn wrote:
> Cos, we track versions in JIRA. There are 230 closed issues for 1.7:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
> We can't just dump all of them to release notes.

Well, a lot of other projects do. And some others don't ;) I guess it depends
on what you want in the RN.

Cos

> On Tue, Aug 2, 2016 at 10:31 PM, Konstantin Boudnik <[hidden email]> wrote:
>
> > Tracking the "Fixed in release" on the JIRA tickets would take care about
> > any
> > gaps pretty much automatically. In general it's a good idea for an RM to
> > run a
> > spring-cleaning on the JIRA tickets to scope up the release. Then once all
> > tickets are fixed, you can simply _generate_ the release notes with a
> > single-button click.
> >
> > Cos
> >
> > On Mon, Aug 01, 2016 at 01:43PM, Pavel Tupitsyn wrote:
> > > Igniters,
> > >
> > > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me.
> > There
> > > are likely more noteworthy changes since 1.6.
> > >
> > > Let's discuss the changes to be included in release notes and fix them.
> > >
> > > Please reply to this email with your proposals.
> > >
> > > Pavel.
> >

[Sergey Kozlov]

Hi, Pavel and Konstantin

Release notes should highlight key features for the released version and
the current list looks good on my mind. But we can put as last item
something like that "Full list of fixed issues
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
"
Also such approach allow us do not repeat "** Many stability and
fault-tolerance fixes.*" from release to release.

On Wed, Aug 3, 2016 at 11:19 PM, Konstantin Boudnik <[hidden email]> wrote:

> On Wed, Aug 03, 2016 at 10:47AM, Pavel Tupitsyn wrote:
> > Cos, we track versions in JIRA. There are 230 closed issues for 1.7:
> > <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%">https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
> > We can't just dump all of them to release notes.
>
> Well, a lot of other projects do. And some others don't ;) I guess it
> depends
> on what you want in the RN.
>
> Cos
>
> > On Tue, Aug 2, 2016 at 10:31 PM, Konstantin Boudnik <[hidden email]>
> wrote:
> >
> > > Tracking the "Fixed in release" on the JIRA tickets would take care
> about
> > > any
> > > gaps pretty much automatically. In general it's a good idea for an RM
> to
> > > run a
> > > spring-cleaning on the JIRA tickets to scope up the release. Then once
> all
> > > tickets are fixed, you can simply _generate_ the release notes with a
> > > single-button click.
> > >
> > > Cos
> > >
> > > On Mon, Aug 01, 2016 at 01:43PM, Pavel Tupitsyn wrote:
> > > > Igniters,
> > > >
> > > > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me.
> > > There
> > > > are likely more noteworthy changes since 1.6.
> > > >
> > > > Let's discuss the changes to be included in release notes and fix
> them.
> > > >
> > > > Please reply to this email with your proposals.
> > > >
> > > > Pavel.
> > >
>

--
Sergey Kozlov
GridGain Systems
www.gridgain.com