Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
MIME-Version: 1.0
In-Reply-To: <CAHpOOhGHYU1=t3fk5jZr3nPAaxqtHP5h=FZTfJS6_QpngUnOxg@mail.gmail.com>
References: <CAGr9p8DzEEW8MwnqYCR1jMWwSqxgUW6vfmgXNb=Cb54ox7i4nw@mail.gmail.com>
 <CAHpOOhGHYU1=t3fk5jZr3nPAaxqtHP5h=FZTfJS6_QpngUnOxg@mail.gmail.com>
From: Robert Metzger <rmetzger@apache.org>
Date: Fri, 23 Jun 2017 14:09:22 +0200
Message-ID: <CAGr9p8Cd4_fxXFiBKiH-pzKmhJvx38aAjaTPnyw7B-uTGqJoaA@mail.gmail.com>
Subject: Re: [DISCUSS] Release 1.3.2 planning
To: "dev@flink.apache.org" <dev@flink.apache.org>
Content-Type: multipart/alternative; boundary="001a11449daefd5f2405529f79d6"
archived-at: Fri, 23 Jun 2017 12:09:46 -0000

--001a11449daefd5f2405529f79d6
Content-Type: text/plain; charset="UTF-8"

Thanks Haohui.

The first main task for the release management is to come up with a
timeline :)
Lets just wait and see which issues get reported. There are currently no
blockers set for 1.3.1 in JIRA.

On Thu, Jun 22, 2017 at 6:47 PM, Haohui Mai <ricetons@gmail.com> wrote:

> Hi,
>
> Release management is though, I'm happy to help. Are there any timelines
> you have in mind?
>
> Haohui
> On Fri, Jun 23, 2017 at 12:01 AM Robert Metzger <rmetzger@apache.org>
> wrote:
>
> > Hi all,
> >
> > with the 1.3.1 release on the way, we can start thinking about the 1.3.2
> > release.
> >
> > We have already one issue that should go in there:
> > - https://issues.apache.org/jira/browse/FLINK-6964
> >
> > If there are any other blockers, let us know here :)
> >
> > I'm wondering if there's somebody from the community who's willing to
> take
> > care of the release management of 1.3.2 :)
> >
>

--001a11449daefd5f2405529f79d6--