You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Denis Magda <dm...@apache.org> on 2020/05/07 20:01:37 UTC
Ignite Releases Plan
Igniters,
Thanks for helping to put together our first roadmap for the rest of 2020
[1]. Turned out to be a handy source that should be appreciated by Ignite
application developers.
By looking at the page, it feels like we can plan a couple of releases:
- Ignite 2.9 (early September) - it includes all the improvements that
should be ready throughout May-July. We reserve August for issues fixing
and final release steps.
- Ignite 2.10 (late January 2021) - the release is for features that
should be completed within the August-November timeframe. Considering the
holiday season, we'll use December and most of January for final release
procedures.
What do you think?
Also, is there anybody who is ready to take over release management tasks
for 2.9?
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
-
Denis
Re: Ignite Releases Plan
Posted by Alexey Goncharuk <al...@gmail.com>.
Maxim,
I am super excited that we start discussing Ignite 3.0, but I think that
leaving only half a year for all the 3.0 changes is overly optimistic.
Moving to a major release allows us to significantly change APIs and
default behavior, storage formats, etc. Honestly, I think just discussions
will take months, let alone the implementation.
Perhaps, we can gradually shape the scope of Ignite 3.0 after Ignite 2.9
while releasing maintenance Ignite releases for 2.x, and set a date for
Ignite 3.0 once there is a clear plan for it.
пт, 8 мая 2020 г. в 13:06, Nikolay Izhikov <ni...@apache.org>:
> +1 to release 2.9 right after 2.8.1
>
> > 8 мая 2020 г., в 12:53, Maxim Muzafarov <mm...@apache.org> написал(а):
> >
> > Folks, Denis,
> >
> >
> > I think no one will argue against that frequent releases is good. The
> > last major 2.8 release scope was frozen the last December, so having
> > the next 2.9 release in September sounds not so good in general. We
> > already have a lot of major features to release, for instance:
> > - Sandbox for user-defined code [1]
> > - .NET: Native Near Cache [2]
> > - TDE - Phase-2. Master key rotation [3]
> > - Thin client: compute support [4]
> >
> > I remember some folks at the last Apache Ignite meetup asking to
> > release the `master key rotation` feature for their production.
> >
> >
> > I suggest the following plan:
> > - Ignite 2.9 (July 2020). Features that are already in the master branch.
> > - Ignite 2.10 (September 2020). Improvements that will be ready
> > throughout May-July.
> > - Ignite 3.0 (January 2020). Improvements that will be completed
> > within the August-November.
> >
> >
> > Some thoughts about Apache Ignite 3.0 release.
> >
> > From my understanding, I think we should release Apache Ignite 3.0 by
> > the end of this year even we would not have super-major features.
> > Keeping backward compatibility for the previous versions which
> > released more than 3 years ago requires a lot of effort. It doubles
> > complexity of each new feature we adding to the product and floods the
> > code with unnecessary if-else statements.
> >
> > I think the beginning of the 2021 year is a good point to stop doing
> > such things and go further :-) We already have the huge wishlist [5]
> > for Apache Ignite 3.0 and we should start removing stale source code
> > from the master branch.
> >
> > WDYT?
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-11410
> > [2] https://issues.apache.org/jira/browse/IGNITE-12691
> > [3] https://issues.apache.org/jira/browse/IGNITE-12186
> > [4] https://issues.apache.org/jira/browse/IGNITE-12835
> > [5]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
> >
> > On Thu, 7 May 2020 at 23:02, Denis Magda <dm...@apache.org> wrote:
> >>
> >> Igniters,
> >>
> >> Thanks for helping to put together our first roadmap for the rest of
> 2020
> >> [1]. Turned out to be a handy source that should be appreciated by
> Ignite
> >> application developers.
> >>
> >> By looking at the page, it feels like we can plan a couple of releases:
> >>
> >> - Ignite 2.9 (early September) - it includes all the improvements that
> >> should be ready throughout May-July. We reserve August for issues
> fixing
> >> and final release steps.
> >> - Ignite 2.10 (late January 2021) - the release is for features that
> >> should be completed within the August-November timeframe. Considering
> the
> >> holiday season, we'll use December and most of January for final
> release
> >> procedures.
> >>
> >>
> >> What do you think?
> >>
> >> Also, is there anybody who is ready to take over release management
> tasks
> >> for 2.9?
> >>
> >> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> >>
> >> -
> >> Denis
>
>
Re: Ignite Releases Plan
Posted by Alexey Zinoviev <za...@gmail.com>.
I suggest to release more often, but I disagree with dates for 2.9. I've
planned to add a few features to 2.9 for ML module (model export/import)
and so on.
If it will be possible to merge in 2.9 branch in June for separate modules,
it's ok for me.
пт, 8 мая 2020 г. в 13:06, Nikolay Izhikov <ni...@apache.org>:
> +1 to release 2.9 right after 2.8.1
>
> > 8 мая 2020 г., в 12:53, Maxim Muzafarov <mm...@apache.org> написал(а):
> >
> > Folks, Denis,
> >
> >
> > I think no one will argue against that frequent releases is good. The
> > last major 2.8 release scope was frozen the last December, so having
> > the next 2.9 release in September sounds not so good in general. We
> > already have a lot of major features to release, for instance:
> > - Sandbox for user-defined code [1]
> > - .NET: Native Near Cache [2]
> > - TDE - Phase-2. Master key rotation [3]
> > - Thin client: compute support [4]
> >
> > I remember some folks at the last Apache Ignite meetup asking to
> > release the `master key rotation` feature for their production.
> >
> >
> > I suggest the following plan:
> > - Ignite 2.9 (July 2020). Features that are already in the master branch.
> > - Ignite 2.10 (September 2020). Improvements that will be ready
> > throughout May-July.
> > - Ignite 3.0 (January 2020). Improvements that will be completed
> > within the August-November.
> >
> >
> > Some thoughts about Apache Ignite 3.0 release.
> >
> > From my understanding, I think we should release Apache Ignite 3.0 by
> > the end of this year even we would not have super-major features.
> > Keeping backward compatibility for the previous versions which
> > released more than 3 years ago requires a lot of effort. It doubles
> > complexity of each new feature we adding to the product and floods the
> > code with unnecessary if-else statements.
> >
> > I think the beginning of the 2021 year is a good point to stop doing
> > such things and go further :-) We already have the huge wishlist [5]
> > for Apache Ignite 3.0 and we should start removing stale source code
> > from the master branch.
> >
> > WDYT?
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-11410
> > [2] https://issues.apache.org/jira/browse/IGNITE-12691
> > [3] https://issues.apache.org/jira/browse/IGNITE-12186
> > [4] https://issues.apache.org/jira/browse/IGNITE-12835
> > [5]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
> >
> > On Thu, 7 May 2020 at 23:02, Denis Magda <dm...@apache.org> wrote:
> >>
> >> Igniters,
> >>
> >> Thanks for helping to put together our first roadmap for the rest of
> 2020
> >> [1]. Turned out to be a handy source that should be appreciated by
> Ignite
> >> application developers.
> >>
> >> By looking at the page, it feels like we can plan a couple of releases:
> >>
> >> - Ignite 2.9 (early September) - it includes all the improvements that
> >> should be ready throughout May-July. We reserve August for issues
> fixing
> >> and final release steps.
> >> - Ignite 2.10 (late January 2021) - the release is for features that
> >> should be completed within the August-November timeframe. Considering
> the
> >> holiday season, we'll use December and most of January for final
> release
> >> procedures.
> >>
> >>
> >> What do you think?
> >>
> >> Also, is there anybody who is ready to take over release management
> tasks
> >> for 2.9?
> >>
> >> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> >>
> >> -
> >> Denis
>
>
Re: Ignite Releases Plan
Posted by Nikolay Izhikov <ni...@apache.org>.
+1 to release 2.9 right after 2.8.1
> 8 мая 2020 г., в 12:53, Maxim Muzafarov <mm...@apache.org> написал(а):
>
> Folks, Denis,
>
>
> I think no one will argue against that frequent releases is good. The
> last major 2.8 release scope was frozen the last December, so having
> the next 2.9 release in September sounds not so good in general. We
> already have a lot of major features to release, for instance:
> - Sandbox for user-defined code [1]
> - .NET: Native Near Cache [2]
> - TDE - Phase-2. Master key rotation [3]
> - Thin client: compute support [4]
>
> I remember some folks at the last Apache Ignite meetup asking to
> release the `master key rotation` feature for their production.
>
>
> I suggest the following plan:
> - Ignite 2.9 (July 2020). Features that are already in the master branch.
> - Ignite 2.10 (September 2020). Improvements that will be ready
> throughout May-July.
> - Ignite 3.0 (January 2020). Improvements that will be completed
> within the August-November.
>
>
> Some thoughts about Apache Ignite 3.0 release.
>
> From my understanding, I think we should release Apache Ignite 3.0 by
> the end of this year even we would not have super-major features.
> Keeping backward compatibility for the previous versions which
> released more than 3 years ago requires a lot of effort. It doubles
> complexity of each new feature we adding to the product and floods the
> code with unnecessary if-else statements.
>
> I think the beginning of the 2021 year is a good point to stop doing
> such things and go further :-) We already have the huge wishlist [5]
> for Apache Ignite 3.0 and we should start removing stale source code
> from the master branch.
>
> WDYT?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-11410
> [2] https://issues.apache.org/jira/browse/IGNITE-12691
> [3] https://issues.apache.org/jira/browse/IGNITE-12186
> [4] https://issues.apache.org/jira/browse/IGNITE-12835
> [5] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
>
> On Thu, 7 May 2020 at 23:02, Denis Magda <dm...@apache.org> wrote:
>>
>> Igniters,
>>
>> Thanks for helping to put together our first roadmap for the rest of 2020
>> [1]. Turned out to be a handy source that should be appreciated by Ignite
>> application developers.
>>
>> By looking at the page, it feels like we can plan a couple of releases:
>>
>> - Ignite 2.9 (early September) - it includes all the improvements that
>> should be ready throughout May-July. We reserve August for issues fixing
>> and final release steps.
>> - Ignite 2.10 (late January 2021) - the release is for features that
>> should be completed within the August-November timeframe. Considering the
>> holiday season, we'll use December and most of January for final release
>> procedures.
>>
>>
>> What do you think?
>>
>> Also, is there anybody who is ready to take over release management tasks
>> for 2.9?
>>
>> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
>>
>> -
>> Denis
Re: Ignite Releases Plan
Posted by Denis Magda <dm...@apache.org>.
Folks,
Let's carry on with this discussion. We're about to start a 2.8.1 vote and
it's good to have this discussion settled once that version is released.
What do you think about my last proposal?
-
Denis
On Fri, May 8, 2020 at 2:21 PM Denis Magda <dm...@apache.org> wrote:
> Maxim, Folks,
>
> Speaking of Ignite 2.9 release time, I would encourage us to wait for all
> those contributors who plan to finish their tasks in June-July. The roadmap
> page shows that we should get ~8 more significant improvements added by
> August. Combining those features with what's already in the master and
> planned to be contributed by Alexey Zinoviev for ML will turn Ignite 2.9
> into the release of the year. I believe it's worth waiting for 2 more
> months. Ignite application developers will have more reasoning to migrate
> from the old versions.
>
> Look, we can do the code freeze in the middle of July and carry on with
> the stabilization by mid of August. Then go ahead and release by the end of
> August or early September (depending on how the vote goes and the overall
> quality). If something is not ready by mid of July then it gets pushed to
> 2.10.
>
> Thoughts?
>
> As for Ignite 3.0, personally I back up Alexey's idea that it's a
> different beast and we need to complete API changes, storage format
> optimizations, start looking into the direct support of Intel Optane
> AppDirect mode that can influence the new storage APIs. We can get back to
> this discussion now using the Ignite 3.0 thread or after rolling out 2.9.
>
> -
> Denis
>
>
> On Fri, May 8, 2020 at 2:53 AM Maxim Muzafarov <mm...@apache.org> wrote:
>
>> Folks, Denis,
>>
>>
>> I think no one will argue against that frequent releases is good. The
>> last major 2.8 release scope was frozen the last December, so having
>> the next 2.9 release in September sounds not so good in general. We
>> already have a lot of major features to release, for instance:
>> - Sandbox for user-defined code [1]
>> - .NET: Native Near Cache [2]
>> - TDE - Phase-2. Master key rotation [3]
>> - Thin client: compute support [4]
>>
>> I remember some folks at the last Apache Ignite meetup asking to
>> release the `master key rotation` feature for their production.
>>
>>
>> I suggest the following plan:
>> - Ignite 2.9 (July 2020). Features that are already in the master branch.
>> - Ignite 2.10 (September 2020). Improvements that will be ready
>> throughout May-July.
>> - Ignite 3.0 (January 2020). Improvements that will be completed
>> within the August-November.
>>
>>
>> Some thoughts about Apache Ignite 3.0 release.
>>
>> From my understanding, I think we should release Apache Ignite 3.0 by
>> the end of this year even we would not have super-major features.
>> Keeping backward compatibility for the previous versions which
>> released more than 3 years ago requires a lot of effort. It doubles
>> complexity of each new feature we adding to the product and floods the
>> code with unnecessary if-else statements.
>>
>> I think the beginning of the 2021 year is a good point to stop doing
>> such things and go further :-) We already have the huge wishlist [5]
>> for Apache Ignite 3.0 and we should start removing stale source code
>> from the master branch.
>>
>> WDYT?
>>
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-11410
>> [2] https://issues.apache.org/jira/browse/IGNITE-12691
>> [3] https://issues.apache.org/jira/browse/IGNITE-12186
>> [4] https://issues.apache.org/jira/browse/IGNITE-12835
>> [5]
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
>>
>> On Thu, 7 May 2020 at 23:02, Denis Magda <dm...@apache.org> wrote:
>> >
>> > Igniters,
>> >
>> > Thanks for helping to put together our first roadmap for the rest of
>> 2020
>> > [1]. Turned out to be a handy source that should be appreciated by
>> Ignite
>> > application developers.
>> >
>> > By looking at the page, it feels like we can plan a couple of releases:
>> >
>> > - Ignite 2.9 (early September) - it includes all the improvements
>> that
>> > should be ready throughout May-July. We reserve August for issues
>> fixing
>> > and final release steps.
>> > - Ignite 2.10 (late January 2021) - the release is for features that
>> > should be completed within the August-November timeframe.
>> Considering the
>> > holiday season, we'll use December and most of January for final
>> release
>> > procedures.
>> >
>> >
>> > What do you think?
>> >
>> > Also, is there anybody who is ready to take over release management
>> tasks
>> > for 2.9?
>> >
>> > [1]
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
>> >
>> > -
>> > Denis
>>
>
Re: Ignite Releases Plan
Posted by Denis Magda <dm...@apache.org>.
Maxim, Folks,
Speaking of Ignite 2.9 release time, I would encourage us to wait for all
those contributors who plan to finish their tasks in June-July. The roadmap
page shows that we should get ~8 more significant improvements added by
August. Combining those features with what's already in the master and
planned to be contributed by Alexey Zinoviev for ML will turn Ignite 2.9
into the release of the year. I believe it's worth waiting for 2 more
months. Ignite application developers will have more reasoning to migrate
from the old versions.
Look, we can do the code freeze in the middle of July and carry on with the
stabilization by mid of August. Then go ahead and release by the end of
August or early September (depending on how the vote goes and the overall
quality). If something is not ready by mid of July then it gets pushed to
2.10.
Thoughts?
As for Ignite 3.0, personally I back up Alexey's idea that it's a different
beast and we need to complete API changes, storage format optimizations,
start looking into the direct support of Intel Optane AppDirect mode that
can influence the new storage APIs. We can get back to this discussion now
using the Ignite 3.0 thread or after rolling out 2.9.
-
Denis
On Fri, May 8, 2020 at 2:53 AM Maxim Muzafarov <mm...@apache.org> wrote:
> Folks, Denis,
>
>
> I think no one will argue against that frequent releases is good. The
> last major 2.8 release scope was frozen the last December, so having
> the next 2.9 release in September sounds not so good in general. We
> already have a lot of major features to release, for instance:
> - Sandbox for user-defined code [1]
> - .NET: Native Near Cache [2]
> - TDE - Phase-2. Master key rotation [3]
> - Thin client: compute support [4]
>
> I remember some folks at the last Apache Ignite meetup asking to
> release the `master key rotation` feature for their production.
>
>
> I suggest the following plan:
> - Ignite 2.9 (July 2020). Features that are already in the master branch.
> - Ignite 2.10 (September 2020). Improvements that will be ready
> throughout May-July.
> - Ignite 3.0 (January 2020). Improvements that will be completed
> within the August-November.
>
>
> Some thoughts about Apache Ignite 3.0 release.
>
> From my understanding, I think we should release Apache Ignite 3.0 by
> the end of this year even we would not have super-major features.
> Keeping backward compatibility for the previous versions which
> released more than 3 years ago requires a lot of effort. It doubles
> complexity of each new feature we adding to the product and floods the
> code with unnecessary if-else statements.
>
> I think the beginning of the 2021 year is a good point to stop doing
> such things and go further :-) We already have the huge wishlist [5]
> for Apache Ignite 3.0 and we should start removing stale source code
> from the master branch.
>
> WDYT?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-11410
> [2] https://issues.apache.org/jira/browse/IGNITE-12691
> [3] https://issues.apache.org/jira/browse/IGNITE-12186
> [4] https://issues.apache.org/jira/browse/IGNITE-12835
> [5]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
>
> On Thu, 7 May 2020 at 23:02, Denis Magda <dm...@apache.org> wrote:
> >
> > Igniters,
> >
> > Thanks for helping to put together our first roadmap for the rest of 2020
> > [1]. Turned out to be a handy source that should be appreciated by Ignite
> > application developers.
> >
> > By looking at the page, it feels like we can plan a couple of releases:
> >
> > - Ignite 2.9 (early September) - it includes all the improvements that
> > should be ready throughout May-July. We reserve August for issues
> fixing
> > and final release steps.
> > - Ignite 2.10 (late January 2021) - the release is for features that
> > should be completed within the August-November timeframe. Considering
> the
> > holiday season, we'll use December and most of January for final
> release
> > procedures.
> >
> >
> > What do you think?
> >
> > Also, is there anybody who is ready to take over release management tasks
> > for 2.9?
> >
> > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> >
> > -
> > Denis
>
Re: Ignite Releases Plan
Posted by Maxim Muzafarov <mm...@apache.org>.
Folks, Denis,
I think no one will argue against that frequent releases is good. The
last major 2.8 release scope was frozen the last December, so having
the next 2.9 release in September sounds not so good in general. We
already have a lot of major features to release, for instance:
- Sandbox for user-defined code [1]
- .NET: Native Near Cache [2]
- TDE - Phase-2. Master key rotation [3]
- Thin client: compute support [4]
I remember some folks at the last Apache Ignite meetup asking to
release the `master key rotation` feature for their production.
I suggest the following plan:
- Ignite 2.9 (July 2020). Features that are already in the master branch.
- Ignite 2.10 (September 2020). Improvements that will be ready
throughout May-July.
- Ignite 3.0 (January 2020). Improvements that will be completed
within the August-November.
Some thoughts about Apache Ignite 3.0 release.
From my understanding, I think we should release Apache Ignite 3.0 by
the end of this year even we would not have super-major features.
Keeping backward compatibility for the previous versions which
released more than 3 years ago requires a lot of effort. It doubles
complexity of each new feature we adding to the product and floods the
code with unnecessary if-else statements.
I think the beginning of the 2021 year is a good point to stop doing
such things and go further :-) We already have the huge wishlist [5]
for Apache Ignite 3.0 and we should start removing stale source code
from the master branch.
WDYT?
[1] https://issues.apache.org/jira/browse/IGNITE-11410
[2] https://issues.apache.org/jira/browse/IGNITE-12691
[3] https://issues.apache.org/jira/browse/IGNITE-12186
[4] https://issues.apache.org/jira/browse/IGNITE-12835
[5] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
On Thu, 7 May 2020 at 23:02, Denis Magda <dm...@apache.org> wrote:
>
> Igniters,
>
> Thanks for helping to put together our first roadmap for the rest of 2020
> [1]. Turned out to be a handy source that should be appreciated by Ignite
> application developers.
>
> By looking at the page, it feels like we can plan a couple of releases:
>
> - Ignite 2.9 (early September) - it includes all the improvements that
> should be ready throughout May-July. We reserve August for issues fixing
> and final release steps.
> - Ignite 2.10 (late January 2021) - the release is for features that
> should be completed within the August-November timeframe. Considering the
> holiday season, we'll use December and most of January for final release
> procedures.
>
>
> What do you think?
>
> Also, is there anybody who is ready to take over release management tasks
> for 2.9?
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
>
> -
> Denis