flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aljoscha Krettek <aljos...@apache.org>
Subject Re: [DISCUSS] Release 1.3.2 planning
Date Fri, 07 Jul 2017 14:03:42 GMT
I think we might have another blocker: https://issues.apache.org/jira/browse/FLINK-7133 <https://issues.apache.org/jira/browse/FLINK-7133>

> On 7. Jul 2017, at 09:18, Haohui Mai <ricetons@gmail.com> wrote:
> 
> I think we are pretty close now -- Jira shows that we're down to two
> blockers: FLINK-7069 and FLINK-6965.
> 
> FLINK-7069 is being merged and we have a PR for FLINK-6965.
> 
> ~Haohui
> 
> On Thu, Jul 6, 2017 at 1:44 AM Aljoscha Krettek <aljoscha@apache.org> wrote:
> 
>> I’m seeing these remaining blockers:
>> https://issues.apache.org/jira/browse/FLINK-7069?filter=12334772&jql=project%20%3D%20FLINK%20AND%20priority%20%3D%20Blocker%20AND%20resolution%20%3D%20Unresolved
>> <
>> https://issues.apache.org/jira/browse/FLINK-7069?filter=12334772&jql=project%20=%20FLINK%20AND%20priority%20=%20Blocker%20AND%20resolution%20=%20Unresolved
>>> 
>> 
>> Could everyone please correctly mark as “blocking” those issues that they
>> consider blocking for 1.3.2 so that we get an accurate overview of where we
>> are.
>> 
>> @Chesnay, could you maybe check if this one should in fact be considered a
>> blocker: https://issues.apache.org/jira/browse/FLINK-7034? <
>> https://issues.apache.org/jira/browse/FLINK-7034?>
>> 
>> Best,
>> Aljoscha
>>> On 6. Jul 2017, at 07:19, Tzu-Li (Gordon) Tai <tzulitai@apache.org>
>> wrote:
>>> 
>>> FLINK-7041 has been merged.
>>> I’d also like to raise another blocker for 1.3.2:
>> https://issues.apache.org/jira/browse/FLINK-6996.
>>> 
>>> Cheers,
>>> Gordon
>>> On 30 June 2017 at 12:46:07 AM, Aljoscha Krettek (aljoscha@apache.org)
>> wrote:
>>> 
>>> Gordon and I found this (in my opinion) blocking issue:
>> https://issues.apache.org/jira/browse/FLINK-7041 <
>> https://issues.apache.org/jira/browse/FLINK-7041>
>>> 
>>> I’m trying to quickly provide a fix.
>>> 
>>>> On 26. Jun 2017, at 15:30, Timo Walther <twalthr@apache.org> wrote:
>>>> 
>>>> I just opened a PR which should be included in the next bug fix release
>> for the Table API:
>>>> https://issues.apache.org/jira/browse/FLINK-7005
>>>> 
>>>> Timo
>>>> 
>>>> Am 23.06.17 um 14:09 schrieb Robert Metzger:
>>>>> 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 :)
>>>>>>> 
>>>> 
>>> 
>> 
>> 


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