ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Zinoviev <zaleslaw....@gmail.com>
Subject Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
Date Fri, 20 Sep 2019 14:24:16 GMT
I wrote about code freeze at  December 18, 2019, ok, we can move one week
earlier to 11 December
Voting + Release could be after 10th January.

пт, 20 сент. 2019 г. в 15:43, Maxim Muzafarov <mmuzaf@apache.org>:

> Alexey,
>
> It is not a problem to shift release a bit later or earlier, but I'm
> strictly against having `code freeze` stage on holidays (the Christmas
> holidays at the end of December and New Year holidays at the beginning
> of January). From my point, it's better to have it completed `code
> freeze` stage before December 23th or started after 10th January.
>
> Thoughts?
>
>
>
> On Fri, 20 Sep 2019 at 15:09, Dmitriy Pavlov <dpavlov@apache.org> wrote:
> >
> > +1 For Maxim as release manager.
> >
> > Maxim,
> >
> > It is a good thing that you have committer rights, and most of the steps
> > you will be able to complete yourself.
> >
> > But please engage one from PMC member to complete steps from the release
> > process where PMC rights are required
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process  At
> > least, access to docker and nuget creds requires PMC membership.
> >
> > Feel free to ping me, I will assist, as well.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> >
> > пт, 20 сент. 2019 г. в 14:59, Alexey Zinoviev <zaleslaw.sin@gmail.com>:
> >
> > > For Spark and ML components the best dates should be moved to one month
> > > later, what's about?
> > > There are a lot of features there, but a lot of bugs and minor
> > > improvements in JIRA too
> > >
> > > Also I support you as a release manager
> > >
> > > Scope Freeze: December 4, 2019
> > > Code Freeze: December 18, 2019
> > > Voting Date: January 10, 2019
> > > Release Date: January 17, 2019
> > >
> > > пт, 20 сент. 2019 г. в 14:44, Maxim Muzafarov <mmuzaf@apache.org>:
> > >
> > > > Igniters,
> > > >
> > > >
> > > > It's almost a year has passed since the last major Apache Ignite 2.7
> > > > has been released. We've accumulated a lot of performance
> improvements
> > > > and a lot of new features which are waiting for their release date.
> > > > Here is my list of the most interesting things from my point since
> the
> > > > last major release:
> > > >
> > > > Service Grid,
> > > > Monitoring,
> > > > Recovery Read
> > > > BLT auto-adjust,
> > > > PDS compression,
> > > > WAL page compression,
> > > > Thin client: best effort affinity,
> > > > Thin client: transactions support (not yet)
> > > > SQL query history
> > > > SQL statistics
> > > >
> > > > I think we should no longer wait and freeze the master branch anymore
> > > > and prepare the next major release by the end of the year.
> > > >
> > > >
> > > > I propose to discuss Time, Scope of Apache Ignite 2.8 release and
> also
> > > > I want to propose myself to be the release manager of the planning
> > > > release.
> > > >
> > > > Scope Freeze: November 4, 2019
> > > > Code Freeze: November 18, 2019
> > > > Voting Date: December 10, 2019
> > > > Release Date: December 17, 2019
> > > >
> > > >
> > > > WDYT?
> > > >
> > >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message