Given the initial feedback, I would like to keep the RC going as well. The upcoming 1.0 release will include the fix and if users complain about it for 0.10 we can do another release in the future.
— +1 for this release. Forwarding my tests from the last vote. Additionally, I’ve verified that the quickstart poms point to the correct version now. – Ufuk > On 09 Feb 2016, at 15:59, Robert Metzger <rmetz...@apache.org> wrote: > > I would also like to keep this RC. 0.10-SNAPSHOT will be equally stable. > > On Tue, Feb 9, 2016 at 2:57 PM, Stephan Ewen <se...@apache.org> wrote: > >> I would be in favor of continuing the release candidate. >> The change is more a feature improvement than a bug, and these should come >> before release candidates (otherwise we never get one done). >> >> The 1.0 release is also very close, so this improvement will be available >> anyways pretty soon. >> >> I personally also invested again quite a bit of time into testing this >> release candidate already. >> >> >> >> On Tue, Feb 9, 2016 at 1:51 PM, Fabian Hueske <fhue...@gmail.com> wrote: >> >>> Thanks Ufuk, >>> +1 for a new RC >>> >>> 2016-02-09 13:49 GMT+01:00 Ufuk Celebi <u...@apache.org>: >>> >>>> Hey Nick, >>>> >>>> I agree that this can be problematic when running multiple jobs on >>>> YARN. Since there is a chance that this might be the last release 0.10 >>>> release, I would be OK to cancel the vote for your fix. >>>> >>>> Still, let's hear the opinion of others before doing this. What do you >>>> think? >>>> >>>> – Ufuk >>>> >>>> >>>> On Mon, Feb 8, 2016 at 8:05 PM, Nick Dimiduk <ndimi...@apache.org> >>> wrote: >>>>> Perhaps too late for the RC, but I've backported FLINK-3293 to this >>>> branch >>>>> via FLINK-3372. Would be nice for those wanting to monitory yarn >>>>> application submissions. >>>>> >>>>> On Mon, Feb 8, 2016 at 9:37 AM, Ufuk Celebi <u...@apache.org> wrote: >>>>> >>>>>> Dear Flink community, >>>>>> >>>>>> Please vote on releasing the following candidate as Apache Flink >>> version >>>>>> 0.10.2. >>>>>> >>>>>> Please note that this vote has a slightly shorter voting period of >> 48 >>>>>> hours. Only a single change has been made since the last release >>>>>> candidate. Since the community has already done extensive testing of >>> the >>>>>> previous release candidate, I'm assuming 48 hours will suffice to >> vote >>>> on >>>>>> this one. >>>>>> >>>>>> The commit to be voted on: >>>>>> e525eb2f1413df238e994d01c909d2b90f1b7709 >>>>>> >>>>>> Branch: >>>>>> release-0.10.2-rc2 (see >>>>>> >>>>>> >>>> >>> >> https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-0.10.2-rc2 >>>>>> ) >>>>>> >>>>>> The release artifacts to be voted on can be found at: >>>>>> http://people.apache.org/~uce/flink-0.10.2-rc2/ >>>>>> >>>>>> The release artifacts are signed with the key with fingerprint >>> 9D403309: >>>>>> http://www.apache.org/dist/flink/KEYS >>>>>> >>>>>> The staging repository for this release can be found at: >>>>>> >>> https://repository.apache.org/content/repositories/orgapacheflink-1061 >>>>>> >>>>>> ------------------------------------------------------------- >>>>>> >>>>>> The vote is open for the next 48 hours and passes if a majority of >> at >>>> least >>>>>> three +1 PMC votes are cast. >>>>>> >>>>>> The vote ends on Wednesday February 10, 2016, 18:45 CET. >>>>>> >>>>>> [ ] +1 Release this package as Apache Flink 0.10.2 >>>>>> [ ] -1 Do not release this package because ... >>>>>> >>>>>> =================================== >>>>>> >>>>>> The following commits have been added since the 0.10.2 RC 1: >>>>>> >>>>>> * 2cd0618 - [tools] Properly update all POM versions in release >> script >>>>>> (3 hours ago) <Ufuk Celebi> >>>>>> >>>> >>> >>
