You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Robert Metzger <rm...@apache.org> on 2017/02/06 19:19:22 UTC
[DISCUSS] Planning Release 1.3
Hi,
according to our recent time-based releases discussion, I came up with the
following deadlines for the upcoming 1.3 release:
*Feature freeze (branch forking)*: 1 May 2017
*Code freeze (first voting RC)*: 15 May 2017
*Release date*: 26 May 2017
I will try to post into this thread monthly to remind everybody on the time
left.
There are currently 21 JIRAs assigned to the 1.3.0 release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.3.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
Re: [DISCUSS] Planning Release 1.3
Posted by Robert Metzger <rm...@apache.org>.
Quick reminder:
*The feature freeze is 1 week from now (May 1)*
On Mon, Mar 6, 2017 at 1:03 PM, Stephan Ewen <se...@apache.org> wrote:
> Looks good to me!
>
>
> On Mon, Mar 6, 2017 at 10:55 AM, Robert Metzger <rm...@apache.org>
> wrote:
>
> > That's the right attitude :)
> >
> > Since one month has passed since my initial email on the 1.3 release,
> > here's a quick reminder for everybody that we have the following
> deadlines:
> >
> > *Feature freeze (branch forking)*: 1 May 2017 (*8 weeks from now*)
> > *Code freeze (first voting RC)*: 15 May 2017
> > *Release date*: 26 May 2017
> >
> >
> >
> > On Mon, Feb 13, 2017 at 6:03 PM, Aljoscha Krettek <al...@apache.org>
> > wrote:
> >
> > > +1, we can do it this time! :-)
> > >
> > > On Mon, 6 Feb 2017 at 20:19 Robert Metzger <rm...@apache.org>
> wrote:
> > >
> > > > Hi,
> > > > according to our recent time-based releases discussion, I came up
> with
> > > the
> > > > following deadlines for the upcoming 1.3 release:
> > > >
> > > > *Feature freeze (branch forking)*: 1 May 2017
> > > > *Code freeze (first voting RC)*: 15 May 2017
> > > > *Release date*: 26 May 2017
> > > >
> > > > I will try to post into this thread monthly to remind everybody on
> the
> > > time
> > > > left.
> > > >
> > > > There are currently 21 JIRAs assigned to the 1.3.0 release:
> > > >
> > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > 3D%20FLINK%20AND%20fixVersion%20%3D%201.3.0%20AND%20resolution%20%3D%
> > > 20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> > > 20DESC%2C%20created%20ASC
> > > >
> > >
> >
>
Re: [DISCUSS] Planning Release 1.3
Posted by Stephan Ewen <se...@apache.org>.
Looks good to me!
On Mon, Mar 6, 2017 at 10:55 AM, Robert Metzger <rm...@apache.org> wrote:
> That's the right attitude :)
>
> Since one month has passed since my initial email on the 1.3 release,
> here's a quick reminder for everybody that we have the following deadlines:
>
> *Feature freeze (branch forking)*: 1 May 2017 (*8 weeks from now*)
> *Code freeze (first voting RC)*: 15 May 2017
> *Release date*: 26 May 2017
>
>
>
> On Mon, Feb 13, 2017 at 6:03 PM, Aljoscha Krettek <al...@apache.org>
> wrote:
>
> > +1, we can do it this time! :-)
> >
> > On Mon, 6 Feb 2017 at 20:19 Robert Metzger <rm...@apache.org> wrote:
> >
> > > Hi,
> > > according to our recent time-based releases discussion, I came up with
> > the
> > > following deadlines for the upcoming 1.3 release:
> > >
> > > *Feature freeze (branch forking)*: 1 May 2017
> > > *Code freeze (first voting RC)*: 15 May 2017
> > > *Release date*: 26 May 2017
> > >
> > > I will try to post into this thread monthly to remind everybody on the
> > time
> > > left.
> > >
> > > There are currently 21 JIRAs assigned to the 1.3.0 release:
> > >
> > > https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%20FLINK%20AND%20fixVersion%20%3D%201.3.0%20AND%20resolution%20%3D%
> > 20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> > 20DESC%2C%20created%20ASC
> > >
> >
>
Re: [DISCUSS] Planning Release 1.3
Posted by Robert Metzger <rm...@apache.org>.
That's the right attitude :)
Since one month has passed since my initial email on the 1.3 release,
here's a quick reminder for everybody that we have the following deadlines:
*Feature freeze (branch forking)*: 1 May 2017 (*8 weeks from now*)
*Code freeze (first voting RC)*: 15 May 2017
*Release date*: 26 May 2017
On Mon, Feb 13, 2017 at 6:03 PM, Aljoscha Krettek <al...@apache.org>
wrote:
> +1, we can do it this time! :-)
>
> On Mon, 6 Feb 2017 at 20:19 Robert Metzger <rm...@apache.org> wrote:
>
> > Hi,
> > according to our recent time-based releases discussion, I came up with
> the
> > following deadlines for the upcoming 1.3 release:
> >
> > *Feature freeze (branch forking)*: 1 May 2017
> > *Code freeze (first voting RC)*: 15 May 2017
> > *Release date*: 26 May 2017
> >
> > I will try to post into this thread monthly to remind everybody on the
> time
> > left.
> >
> > There are currently 21 JIRAs assigned to the 1.3.0 release:
> >
> > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20FLINK%20AND%20fixVersion%20%3D%201.3.0%20AND%20resolution%20%3D%
> 20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> 20DESC%2C%20created%20ASC
> >
>
Re: [DISCUSS] Planning Release 1.3
Posted by Aljoscha Krettek <al...@apache.org>.
+1, we can do it this time! :-)
On Mon, 6 Feb 2017 at 20:19 Robert Metzger <rm...@apache.org> wrote:
> Hi,
> according to our recent time-based releases discussion, I came up with the
> following deadlines for the upcoming 1.3 release:
>
> *Feature freeze (branch forking)*: 1 May 2017
> *Code freeze (first voting RC)*: 15 May 2017
> *Release date*: 26 May 2017
>
> I will try to post into this thread monthly to remind everybody on the time
> left.
>
> There are currently 21 JIRAs assigned to the 1.3.0 release:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.3.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
Re: [DISCUSS] Planning Release 1.3
Posted by Kostas Kloudas <k....@data-artisans.com>.
+1
On Feb 6, 2017 20:19, "Robert Metzger" <rm...@apache.org> wrote:
> Hi,
> according to our recent time-based releases discussion, I came up with the
> following deadlines for the upcoming 1.3 release:
>
> *Feature freeze (branch forking)*: 1 May 2017
> *Code freeze (first voting RC)*: 15 May 2017
> *Release date*: 26 May 2017
>
> I will try to post into this thread monthly to remind everybody on the time
> left.
>
> There are currently 21 JIRAs assigned to the 1.3.0 release:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20FLINK%20AND%20fixVersion%20%3D%201.3.0%20AND%20resolution%20%3D%
> 20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> 20DESC%2C%20created%20ASC
>