Hey all,

although there was no feedback for this preview RC, most of the issues
mentioned in the release are either resolved or open PRs. Once the
following PRs have been merged, I would like to create RC1 and the
release-1.1 branch. Feedback to this list is highly appreciated.

Open PRs (awaiting review/review in progress):
- https://github.com/apache/flink/pull/2276: Forward suspend to
checkpoint coordinator
- https://github.com/apache/flink/pull/2257: Allow re-registration of
TMs at resource manager
- https://github.com/apache/flink/pull/2226: Move Metrics API to separate module

Open PRs (to be merged):
- https://github.com/apache/flink/pull/2273: Only allow/require query
for Tuple Stream in CassandraSink
- https://github.com/apache/flink/pull/2271: Add restarting time JM metric
- https://github.com/apache/flink/pull/2256: Don't clean up BlobStore
on BlobServer shut down
- https://github.com/apache/flink/pull/2194: Add savepoint headers

Open issues w/o PRs:
- https://issues.apache.org/jira/browse/FLINK-4239: Set Default
Allowed Lateness to Zero and Make Triggers Non-Purging
- https://issues.apache.org/jira/browse/FLINK-4207: WindowOperator
becomes very slow with allowed lateness

@Aljoscha, Kostas: do you have an idea when these will be addressed?

On Mon, Jul 18, 2016 at 11:05 AM, Aljoscha Krettek <aljos...@apache.org> wrote:
> Not yet, but Kostas is investigating.
>
> On Fri, 15 Jul 2016 at 18:21 Ufuk Celebi <u...@apache.org> wrote:
>
>> Most actually have a pending PR, except:
>> https://issues.apache.org/jira/browse/FLINK-4207,
>> https://issues.apache.org/jira/browse/FLINK-4201.
>>
>> I will assign FLINK-4201 to myself and hope to fix it over the
>> weekend. The issue Stefan mentioned also has a pending PR by now.
>>
>> Hope to create the first RC next week... @Aljoscha, Stephan: any idea
>> about fixing FLINK-4207?
>>
>> – Ufuk
>>
>> On Fri, Jul 15, 2016 at 4:21 PM, Robert Metzger <rmetz...@apache.org>
>> wrote:
>> > There are still 7 blockers for the release:
>> >
>> https://issues.apache.org/jira/browse/FLINK-4207?jql=project%20%3D%20FLINK%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC
>> > most of them are assigned, some even have a pending pull request.
>> >
>> > On Thu, Jul 7, 2016 at 11:26 AM, Stefan Richter <
>> s.rich...@data-artisans.com
>> >> wrote:
>> >
>> >> Hi Ufuk,
>> >>
>> >> Thanks for starting this thread. I think we should solve
>> >> https://issues.apache.org/jira/browse/FLINK-4166 <
>> >> https://issues.apache.org/jira/browse/FLINK-4166> for this version,
>> >> because it can easily become a blocker when running multiple Flink
>> >> applications on a clusters with HA  (see related issue for one example).
>> >>
>> >> > Am 07.07.2016 um 11:02 schrieb Ufuk Celebi <u...@apache.org>:
>> >> >
>> >> > Dear community,
>> >> >
>> >> > ===============
>> >> > FLINK 1.1.0 RC0
>> >> > ===============
>> >> >
>> >> > I've now created a "preview RC" for the upcoming 1.1.0 release,
>> >> > including everything in master up to cb7824
>> >> > (https://github.com/uce/flink/tree/release-1.1.0-rc0).
>> >> >
>> >> > There are still some blocking issues and important pull requests to be
>> >> > merged (see below), but nevertheless I would like to start testing
>> >> > Flink for the release in order to get the process going.
>> >> >
>> >> > In past major releases, we needed to create many release candidates,
>> >> > often for fixing just some small issues. I would like to speed up the
>> >> > release process by collecting the last remaining issues with the RC0.
>> >> > Once these issues are resolved, we can start voting on RC1. This is
>> >> > also when I will create the release-1.1 branch.
>> >> >
>> >> > We have a Wiki page
>> >> > https://cwiki.apache.org/confluence/display/FLINK/Releasing
>> containing
>> >> > some common release verification tasks.
>> >> >
>> >> > Also, production users are encouraged to participate in the release
>> >> > verification process.
>> >> >
>> >> > Here are the preview binaries located:
>> >> > http://home.apache.org/~uce/flink-1.1.0-rc0/
>> >> >
>> >> > This is the staging repository:
>> >> >
>> https://repository.apache.org/content/repositories/orgapacheflink-1097
>> >> >
>> >> > To use the release candidate in an existing Maven project, set the
>> >> > Flink version to 1.1.0 and the repository URL to
>> >> >
>> https://repository.apache.org/content/repositories/orgapacheflink-1097.
>> >> >
>> >> > The POM should look like this:
>> >> >
>> >> > <properties>
>> >> >   <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
>> >> >   <flink.version>1.1.0</flink.version>
>> >> > </properties>
>> >> >
>> >> > <repositories>
>> >> >   <repository>
>> >> >      <id>flink.release-staging</id>
>> >> >      <name>Apache Development Snapshot Repository</name>
>> >> >      <url>
>> >> https://repository.apache.org/content/repositories/orgapacheflink-1097
>> >> </url>
>> >> >      <releases><enabled>true</enabled></releases>
>> >> >      <snapshots><enabled>false</enabled></snapshots>
>> >> >   </repository>
>> >> > </repositories>
>> >> >
>> >> > ===========
>> >> > OPEN ISSUES
>> >> > ===========
>> >> >
>> >> > The following are important to be fixed/merged before the release:
>> >> > - Savepoint headers: PR #2083 (
>> https://github.com/apache/flink/pull/2083
>> >> )
>> >> >  * includes FLINK-4154 (
>> https://issues.apache.org/jira/browse/FLINK-4154
>> >> )
>> >> > - Savepoint disposal with user class loader: #2194
>> >> > (https://github.com/apache/flink/pull/2194)
>> >> > - Cassandra sink exception check: #2183
>> >> > (https://github.com/apache/flink/pull/2183)
>> >> > - Prevent Metrics log flooding: #2135
>> >> > (https://github.com/apache/flink/pull/2135)
>> >> > - CEP serialization: #2202 (https://github.com/apache/flink/pull/2202
>> )
>> >> > - HA BLOB store life-cycle:
>> >> https://issues.apache.org/jira/browse/FLINK-4150
>> >> >
>> >> > Nice to have:
>> >> > - Hash-based combine: #1517 https://github.com/apache/flink/pull/1517
>> >> >
>> >> > Feel free to add issues/PRs to the list and please report any issues
>> >> > you encounter during testing in this thread.
>> >>
>> >>
>>

Reply via email to