Agreed, as I said above: >>>> I have the fix ready but we can do that in Flink 1.2.2. Very quickly, >>>> though.
Best, Aljoscha > On 24. Apr 2017, at 13:19, Ufuk Celebi <u...@apache.org> wrote: > > I agree with Till and would NOT cancel this release. It has been > delayed already quite a bit already and the feature freeze for 1.3.0 > is coming up (i.e. most contributors will be busy and not spend a lot > of time for 1.2.1). > > – Ufuk > > > On Mon, Apr 24, 2017 at 9:31 AM, Till Rohrmann <trohrm...@apache.org> wrote: >> If this bug was already present in 1.2.0, then I guess not many users have >> used this feature. Otherwise we would have seen complaints on the mailing >> list. >> >> From the JIRA issue description, it looks as if we have to fix it for 1.3.0 >> anyway. What about fixing it this week and then backporting it to the 1.2.1 >> branch? >> >> Cheers, >> Till >> >> On Mon, Apr 24, 2017 at 8:12 AM, Aljoscha Krettek <aljos...@apache.org> >> wrote: >> >>> It means that users cannot restore from 1.2.0 to 1.2.0, 1.2.0 to 1.2.1, or >>> 1.2.1 to 1.2.1. However, this only happens when using the >>> CheckpointedRestoring interface, which you have to do when you want to >>> migrate away form the Checkpointed interface. >>> >>> tl;dr It’s not a new bug but one that was present in 1.2.0 already. >>> >>>> On 23. Apr 2017, at 21:16, Robert Metzger <rmetz...@apache.org> wrote: >>>> >>>> @all: I'm sorry for being a bad release manager this time. I'm not >>> spending >>>> much time online these days. I hope to increase my dev@ list activity a >>>> little bit next week. >>>> >>>> @Aljoscha: >>>> Does this mean that users can not upgrade from 1.2.0 to 1.2.1 ? >>>> >>>> Can we make the minor versions easily compatible? >>>> If so, I would prefer to cancel this release as well and do another one. >>>> >>>> >>>> On Fri, Apr 21, 2017 at 12:04 PM, Aljoscha Krettek <aljos...@apache.org> >>>> wrote: >>>> >>>>> There is this (somewhat pesky) issue: >>>>> - https://issues.apache.org/jira/browse/FLINK-6353: Restoring using >>>>> CheckpointedRestoring does not work from 1.2 to 1.2 >>>>> >>>>> I have the fix ready but we can do that in Flink 1.2.2. Very quickly, >>>>> though. >>>>> >>>>>> On 20. Apr 2017, at 17:20, Henry Saputra <henry.sapu...@gmail.com> >>>>> wrote: >>>>>> >>>>>> LICENSE file exists >>>>>> NOTICE file looks good >>>>>> Signature files look good >>>>>> Hash files look good >>>>>> No 3rd party exes in source artifact >>>>>> Source compiled and pass tests >>>>>> Local run work >>>>>> Run simple job on YARN >>>>>> >>>>>> +1 >>>>>> >>>>>> - Henry >>>>>> >>>>>> On Wed, Apr 12, 2017 at 4:06 PM, Robert Metzger <rmetz...@apache.org> >>>>> wrote: >>>>>> >>>>>>> Dear Flink community, >>>>>>> >>>>>>> Please vote on releasing the following candidate as Apache Flink >>> version >>>>>>> 1.2 >>>>>>> .1. >>>>>>> >>>>>>> The commit to be voted on: >>>>>>> 76eba4e0 <http://git-wip-us.apache.org/repos/asf/flink/commit/ >>> 76eba4e0> >>>>>>> (*http://git-wip-us.apache.org/repos/asf/flink/commit/76eba4e0 >>>>>>> <http://git-wip-us.apache.org/repos/asf/flink/commit/76eba4e0>*) >>>>>>> >>>>>>> Branch: >>>>>>> release-1.2.1-rc2 >>>>>>> >>>>>>> The release artifacts to be voted on can be found at: >>>>>>> http://people.apache.org/~rmetzger/flink-1.2.1-rc2/ >>>>>>> >>>>>>> >>>>>>> The release artifacts are signed with the key with fingerprint >>> D9839159: >>>>>>> http://www.apache.org/dist/flink/KEYS >>>>>>> >>>>>>> The staging repository for this release can be found at: >>>>>>> *https://repository.apache.org/content/repositories/ >>> orgapacheflink-1117 >>>>>>> <https://repository.apache.org/content/repositories/ >>> orgapacheflink-1117 >>>>>> * >>>>>>> >>>>>>> ------------------------------------------------------------- >>>>>>> >>>>>>> >>>>>>> The vote ends on Tuesday, 1pm CET. >>>>>>> >>>>>>> [ ] +1 Release this package as Apache Flink 1.2.1 >>>>>>> [ ] -1 Do not release this package, because ... >>>>>>> >>>>> >>>>> >>> >>>
