You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Tzu-Li (Gordon) Tai" <tz...@apache.org> on 2017/07/06 05:19:16 UTC
Re: [DISCUSS] Release 1.3.2 planning
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 <tw...@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 <ri...@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 <rm...@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 :)
>>>>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Aljoscha Krettek <al...@apache.org>.
Alright, it's always good to be extra careful here. 👍
> On 28. Jul 2017, at 14:59, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>
> I also was thinking that FLINK-6215 shouldn’t block 1.3.2, just wanted to make sure due to the previous comments mentioned on the PR. Agreed ;)
>
> Cheers,
> Gordon
>
> On 28 July 2017 at 8:39:05 PM, Aljoscha Krettek (aljoscha@apache.org) wrote:
>
> I think we don't have to consider that since no-one (aside from testing) ever ran into problems with that. However, we should keep in mind merging this for 1.4 (and 1.3.3). What do you think?
>
> Best,
> Aljoscha
>
>> On 28. Jul 2017, at 14:35, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>>
>> Would https://github.com/apache/flink/pull/3669 (Make StatefulSequenceSource rescalable) be considered another blocker / important fix for 1.3.2?
>>
>> Was scanning some PRs and noticed that there were previous comments on needing to merge that fix for release-1.3.
>> One specific aspect I’m not sure of whether or not to consider it a blocker is if there are actually users using the StatefulSequenceSource in production, and if so, we would need to do a bit more work on the source to make it backwards compatible (as of now, the changes in the PR do not provide backwards compatibility).
>>
>> What do you think?
>>
>> - Gordon
>> On 25 July 2017 at 11:02:05 PM, Aljoscha Krettek (aljoscha@apache.org) wrote:
>>
>> I did some preliminary cluster testing on 1.3-SNAPSHOT and it seems there is another issue in RocksDB with incremental checkpoints. Stefan and I are currently investigating. I'll keep you posted and we can hopefully create an RC once we hunt this one down.
>>
>> Best,
>> Aljoscha
>>
>>> On 24. Jul 2017, at 14:39, Timo Walther <tw...@apache.org> wrote:
>>>
>>> I just merged the fixes for FLINK-7137 and FLINK-7177. All blockers are resolved from the Table & SQL API side.
>>>
>>> Regards,
>>> Timo
>>>
>>> Am 24.07.17 um 11:14 schrieb Aljoscha Krettek:
>>>> @Greg: I merged that.
>>>>
>>>> It seems like all blockers are now either resolved or determined not to be blocking for this release. I will try and cut the first RC now.
>>>>
>>>> Best,
>>>> Aljoscha
>>>>
>>>>> On 21. Jul 2017, at 19:07, Greg Hogan <co...@greghogan.com> wrote:
>>>>>
>>>>> FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2.
>>>>>
>>>>>
>>>>>> On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>>>>>>
>>>>>> I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
>>>>>>
>>>>>> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
>>>>>>
>>>>>> Hi Aljoscha,
>>>>>> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
>>>>>> in 1.3.2, if it makes sense.
>>>>>>
>>>>>> Thanks,
>>>>>> Bowen
>>>>>>
>>>>>> On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Short update, we resolved some blockers and discovered some new ones.
>>>>>>> There’s this nifty Jira page if you want to keep track:
>>>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
>>>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>>>>>>>
>>>>>>> Once again, could everyone please update the Jira issues that they think
>>>>>>> should be release blocking. I would like to start building release
>>>>>>> candidates at the end of this week, if possible.
>>>>>>>
>>>>>>> And yes, I’m volunteering to be the release manager on this release. ;-)
>>>>>>>
>>>>>>> Best,
>>>>>>> Aljoscha
>>>>>>>
>>>>>>>> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>>>>>>>>
>>>>>>>> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
>>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>
>>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by "Tzu-Li (Gordon) Tai" <tz...@apache.org>.
I also was thinking that FLINK-6215 shouldn’t block 1.3.2, just wanted to make sure due to the previous comments mentioned on the PR. Agreed ;)
Cheers,
Gordon
On 28 July 2017 at 8:39:05 PM, Aljoscha Krettek (aljoscha@apache.org) wrote:
I think we don't have to consider that since no-one (aside from testing) ever ran into problems with that. However, we should keep in mind merging this for 1.4 (and 1.3.3). What do you think?
Best,
Aljoscha
> On 28. Jul 2017, at 14:35, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>
> Would https://github.com/apache/flink/pull/3669 (Make StatefulSequenceSource rescalable) be considered another blocker / important fix for 1.3.2?
>
> Was scanning some PRs and noticed that there were previous comments on needing to merge that fix for release-1.3.
> One specific aspect I’m not sure of whether or not to consider it a blocker is if there are actually users using the StatefulSequenceSource in production, and if so, we would need to do a bit more work on the source to make it backwards compatible (as of now, the changes in the PR do not provide backwards compatibility).
>
> What do you think?
>
> - Gordon
> On 25 July 2017 at 11:02:05 PM, Aljoscha Krettek (aljoscha@apache.org) wrote:
>
> I did some preliminary cluster testing on 1.3-SNAPSHOT and it seems there is another issue in RocksDB with incremental checkpoints. Stefan and I are currently investigating. I'll keep you posted and we can hopefully create an RC once we hunt this one down.
>
> Best,
> Aljoscha
>
>> On 24. Jul 2017, at 14:39, Timo Walther <tw...@apache.org> wrote:
>>
>> I just merged the fixes for FLINK-7137 and FLINK-7177. All blockers are resolved from the Table & SQL API side.
>>
>> Regards,
>> Timo
>>
>> Am 24.07.17 um 11:14 schrieb Aljoscha Krettek:
>>> @Greg: I merged that.
>>>
>>> It seems like all blockers are now either resolved or determined not to be blocking for this release. I will try and cut the first RC now.
>>>
>>> Best,
>>> Aljoscha
>>>
>>>> On 21. Jul 2017, at 19:07, Greg Hogan <co...@greghogan.com> wrote:
>>>>
>>>> FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2.
>>>>
>>>>
>>>>> On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>>>>>
>>>>> I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
>>>>>
>>>>> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
>>>>>
>>>>> Hi Aljoscha,
>>>>> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
>>>>> in 1.3.2, if it makes sense.
>>>>>
>>>>> Thanks,
>>>>> Bowen
>>>>>
>>>>> On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Short update, we resolved some blockers and discovered some new ones.
>>>>>> There’s this nifty Jira page if you want to keep track:
>>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
>>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>>>>>>
>>>>>> Once again, could everyone please update the Jira issues that they think
>>>>>> should be release blocking. I would like to start building release
>>>>>> candidates at the end of this week, if possible.
>>>>>>
>>>>>> And yes, I’m volunteering to be the release manager on this release. ;-)
>>>>>>
>>>>>> Best,
>>>>>> Aljoscha
>>>>>>
>>>>>>> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>>>>>>>
>>>>>>> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
>>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>
>>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Aljoscha Krettek <al...@apache.org>.
I think we don't have to consider that since no-one (aside from testing) ever ran into problems with that. However, we should keep in mind merging this for 1.4 (and 1.3.3). What do you think?
Best,
Aljoscha
> On 28. Jul 2017, at 14:35, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>
> Would https://github.com/apache/flink/pull/3669 (Make StatefulSequenceSource rescalable) be considered another blocker / important fix for 1.3.2?
>
> Was scanning some PRs and noticed that there were previous comments on needing to merge that fix for release-1.3.
> One specific aspect I’m not sure of whether or not to consider it a blocker is if there are actually users using the StatefulSequenceSource in production, and if so, we would need to do a bit more work on the source to make it backwards compatible (as of now, the changes in the PR do not provide backwards compatibility).
>
> What do you think?
>
> - Gordon
> On 25 July 2017 at 11:02:05 PM, Aljoscha Krettek (aljoscha@apache.org) wrote:
>
> I did some preliminary cluster testing on 1.3-SNAPSHOT and it seems there is another issue in RocksDB with incremental checkpoints. Stefan and I are currently investigating. I'll keep you posted and we can hopefully create an RC once we hunt this one down.
>
> Best,
> Aljoscha
>
>> On 24. Jul 2017, at 14:39, Timo Walther <tw...@apache.org> wrote:
>>
>> I just merged the fixes for FLINK-7137 and FLINK-7177. All blockers are resolved from the Table & SQL API side.
>>
>> Regards,
>> Timo
>>
>> Am 24.07.17 um 11:14 schrieb Aljoscha Krettek:
>>> @Greg: I merged that.
>>>
>>> It seems like all blockers are now either resolved or determined not to be blocking for this release. I will try and cut the first RC now.
>>>
>>> Best,
>>> Aljoscha
>>>
>>>> On 21. Jul 2017, at 19:07, Greg Hogan <co...@greghogan.com> wrote:
>>>>
>>>> FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2.
>>>>
>>>>
>>>>> On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>>>>>
>>>>> I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
>>>>>
>>>>> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
>>>>>
>>>>> Hi Aljoscha,
>>>>> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
>>>>> in 1.3.2, if it makes sense.
>>>>>
>>>>> Thanks,
>>>>> Bowen
>>>>>
>>>>> On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Short update, we resolved some blockers and discovered some new ones.
>>>>>> There’s this nifty Jira page if you want to keep track:
>>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
>>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>>>>>>
>>>>>> Once again, could everyone please update the Jira issues that they think
>>>>>> should be release blocking. I would like to start building release
>>>>>> candidates at the end of this week, if possible.
>>>>>>
>>>>>> And yes, I’m volunteering to be the release manager on this release. ;-)
>>>>>>
>>>>>> Best,
>>>>>> Aljoscha
>>>>>>
>>>>>>> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>>>>>>>
>>>>>>> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
>>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>
>>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by "Tzu-Li (Gordon) Tai" <tz...@apache.org>.
Would https://github.com/apache/flink/pull/3669 (Make StatefulSequenceSource rescalable) be considered another blocker / important fix for 1.3.2?
Was scanning some PRs and noticed that there were previous comments on needing to merge that fix for release-1.3.
One specific aspect I’m not sure of whether or not to consider it a blocker is if there are actually users using the StatefulSequenceSource in production, and if so, we would need to do a bit more work on the source to make it backwards compatible (as of now, the changes in the PR do not provide backwards compatibility).
What do you think?
- Gordon
On 25 July 2017 at 11:02:05 PM, Aljoscha Krettek (aljoscha@apache.org) wrote:
I did some preliminary cluster testing on 1.3-SNAPSHOT and it seems there is another issue in RocksDB with incremental checkpoints. Stefan and I are currently investigating. I'll keep you posted and we can hopefully create an RC once we hunt this one down.
Best,
Aljoscha
> On 24. Jul 2017, at 14:39, Timo Walther <tw...@apache.org> wrote:
>
> I just merged the fixes for FLINK-7137 and FLINK-7177. All blockers are resolved from the Table & SQL API side.
>
> Regards,
> Timo
>
> Am 24.07.17 um 11:14 schrieb Aljoscha Krettek:
>> @Greg: I merged that.
>>
>> It seems like all blockers are now either resolved or determined not to be blocking for this release. I will try and cut the first RC now.
>>
>> Best,
>> Aljoscha
>>
>>> On 21. Jul 2017, at 19:07, Greg Hogan <co...@greghogan.com> wrote:
>>>
>>> FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2.
>>>
>>>
>>>> On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>>>>
>>>> I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
>>>>
>>>> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
>>>>
>>>> Hi Aljoscha,
>>>> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
>>>> in 1.3.2, if it makes sense.
>>>>
>>>> Thanks,
>>>> Bowen
>>>>
>>>> On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
>>>> wrote:
>>>>
>>>>> Short update, we resolved some blockers and discovered some new ones.
>>>>> There’s this nifty Jira page if you want to keep track:
>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>>>>>
>>>>> Once again, could everyone please update the Jira issues that they think
>>>>> should be release blocking. I would like to start building release
>>>>> candidates at the end of this week, if possible.
>>>>>
>>>>> And yes, I’m volunteering to be the release manager on this release. ;-)
>>>>>
>>>>> Best,
>>>>> Aljoscha
>>>>>
>>>>>> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>>>>>>
>>>>>> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
>>>>>>>>>>>>>
>>>>>>>>
>>>>>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Aljoscha Krettek <al...@apache.org>.
I did some preliminary cluster testing on 1.3-SNAPSHOT and it seems there is another issue in RocksDB with incremental checkpoints. Stefan and I are currently investigating. I'll keep you posted and we can hopefully create an RC once we hunt this one down.
Best,
Aljoscha
> On 24. Jul 2017, at 14:39, Timo Walther <tw...@apache.org> wrote:
>
> I just merged the fixes for FLINK-7137 and FLINK-7177. All blockers are resolved from the Table & SQL API side.
>
> Regards,
> Timo
>
> Am 24.07.17 um 11:14 schrieb Aljoscha Krettek:
>> @Greg: I merged that.
>>
>> It seems like all blockers are now either resolved or determined not to be blocking for this release. I will try and cut the first RC now.
>>
>> Best,
>> Aljoscha
>>
>>> On 21. Jul 2017, at 19:07, Greg Hogan <co...@greghogan.com> wrote:
>>>
>>> FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2.
>>>
>>>
>>>> On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>>>>
>>>> I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
>>>>
>>>> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
>>>>
>>>> Hi Aljoscha,
>>>> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
>>>> in 1.3.2, if it makes sense.
>>>>
>>>> Thanks,
>>>> Bowen
>>>>
>>>> On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
>>>> wrote:
>>>>
>>>>> Short update, we resolved some blockers and discovered some new ones.
>>>>> There’s this nifty Jira page if you want to keep track:
>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
>>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>>>>>
>>>>> Once again, could everyone please update the Jira issues that they think
>>>>> should be release blocking. I would like to start building release
>>>>> candidates at the end of this week, if possible.
>>>>>
>>>>> And yes, I’m volunteering to be the release manager on this release. ;-)
>>>>>
>>>>> Best,
>>>>> Aljoscha
>>>>>
>>>>>> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>>>>>>
>>>>>> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
>>>>>>>>>>>>>
>>>>>>>>
>>>>>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Timo Walther <tw...@apache.org>.
I just merged the fixes for FLINK-7137 and FLINK-7177. All blockers are
resolved from the Table & SQL API side.
Regards,
Timo
Am 24.07.17 um 11:14 schrieb Aljoscha Krettek:
> @Greg: I merged that.
>
> It seems like all blockers are now either resolved or determined not to be blocking for this release. I will try and cut the first RC now.
>
> Best,
> Aljoscha
>
>> On 21. Jul 2017, at 19:07, Greg Hogan <co...@greghogan.com> wrote:
>>
>> FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2.
>>
>>
>>> On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>>>
>>> I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
>>>
>>> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
>>>
>>> Hi Aljoscha,
>>> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
>>> in 1.3.2, if it makes sense.
>>>
>>> Thanks,
>>> Bowen
>>>
>>> On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
>>> wrote:
>>>
>>>> Short update, we resolved some blockers and discovered some new ones.
>>>> There’s this nifty Jira page if you want to keep track:
>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
>>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>>>>
>>>> Once again, could everyone please update the Jira issues that they think
>>>> should be release blocking. I would like to start building release
>>>> candidates at the end of this week, if possible.
>>>>
>>>> And yes, I’m volunteering to be the release manager on this release. ;-)
>>>>
>>>> Best,
>>>> Aljoscha
>>>>
>>>>> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>>>>>
>>>>> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
>>>>>>>>>>>>
>>>>>>>
>>>>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Aljoscha Krettek <al...@apache.org>.
@Greg: I merged that.
It seems like all blockers are now either resolved or determined not to be blocking for this release. I will try and cut the first RC now.
Best,
Aljoscha
> On 21. Jul 2017, at 19:07, Greg Hogan <co...@greghogan.com> wrote:
>
> FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2.
>
>
>> On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>>
>> I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
>>
>> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
>>
>> Hi Aljoscha,
>> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
>> in 1.3.2, if it makes sense.
>>
>> Thanks,
>> Bowen
>>
>> On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
>> wrote:
>>
>>> Short update, we resolved some blockers and discovered some new ones.
>>> There’s this nifty Jira page if you want to keep track:
>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
>>> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>>>
>>> Once again, could everyone please update the Jira issues that they think
>>> should be release blocking. I would like to start building release
>>> candidates at the end of this week, if possible.
>>>
>>> And yes, I’m volunteering to be the release manager on this release. ;-)
>>>
>>> Best,
>>> Aljoscha
>>>
>>>> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>>>>
>>>> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
>>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Greg Hogan <co...@greghogan.com>.
FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2.
> On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai <tz...@apache.org> wrote:
>
> I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
>
> On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
>
> Hi Aljoscha,
> I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
> in 1.3.2, if it makes sense.
>
> Thanks,
> Bowen
>
> On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
> wrote:
>
>> Short update, we resolved some blockers and discovered some new ones.
>> There’s this nifty Jira page if you want to keep track:
>> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
>> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>>
>> Once again, could everyone please update the Jira issues that they think
>> should be release blocking. I would like to start building release
>> candidates at the end of this week, if possible.
>>
>> And yes, I’m volunteering to be the release manager on this release. ;-)
>>
>> Best,
>> Aljoscha
>>
>>> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>>>
>>> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
>>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>
>>
Re: [DISCUSS] Release 1.3.2 planning
Posted by "Tzu-Li (Gordon) Tai" <tz...@apache.org>.
I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll update its priority.
On 13 July 2017 at 4:06:06 PM, Bowen Li (bowen.li@offerupnow.com) wrote:
Hi Aljoscha,
I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
in 1.3.2, if it makes sense.
Thanks,
Bowen
On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
wrote:
> Short update, we resolved some blockers and discovered some new ones.
> There’s this nifty Jira page if you want to keep track:
> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>
> Once again, could everyone please update the Jira issues that they think
> should be release blocking. I would like to start building release
> candidates at the end of this week, if possible.
>
> And yes, I’m volunteering to be the release manager on this release. ;-)
>
> Best,
> Aljoscha
>
> > On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
> >
> > 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
> >>>>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >
>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Bowen Li <bo...@offerupnow.com>.
Hi Aljoscha,
I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
in 1.3.2, if it makes sense.
Thanks,
Bowen
On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek <al...@apache.org>
wrote:
> Short update, we resolved some blockers and discovered some new ones.
> There’s this nifty Jira page if you want to keep track:
> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>
> Once again, could everyone please update the Jira issues that they think
> should be release blocking. I would like to start building release
> candidates at the end of this week, if possible.
>
> And yes, I’m volunteering to be the release manager on this release. ;-)
>
> Best,
> Aljoscha
>
> > On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
> >
> > 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 :)
> >>>>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >
>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Aljoscha Krettek <al...@apache.org>.
Short update, we resolved some blockers and discovered some new ones. There’s this nifty Jira page if you want to keep track: https://issues.apache.org/jira/projects/FLINK/versions/12340984 <https://issues.apache.org/jira/projects/FLINK/versions/12340984>
Once again, could everyone please update the Jira issues that they think should be release blocking. I would like to start building release candidates at the end of this week, if possible.
And yes, I’m volunteering to be the release manager on this release. ;-)
Best,
Aljoscha
> On 7. Jul 2017, at 16:03, Aljoscha Krettek <al...@apache.org> wrote:
>
> 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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 <rm...@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 :)
>>>>>>>>
>>>>>
>>>>
>>>
>>>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Aljoscha Krettek <al...@apache.org>.
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 <ri...@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 <al...@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 <tz...@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 <tw...@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 <ri...@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 <rm...@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 :)
>>>>>>>
>>>>
>>>
>>
>>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Haohui Mai <ri...@gmail.com>.
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 <al...@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 <tz...@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 <tw...@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 <ri...@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 <rm...@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 :)
> >>>>>
> >>
> >
>
>
Re: [DISCUSS] Release 1.3.2 planning
Posted by Aljoscha Krettek <al...@apache.org>.
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 <tz...@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 <tw...@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 <ri...@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 <rm...@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 :)
>>>>>
>>
>