Return-Path: X-Original-To: apmail-flink-user-archive@minotaur.apache.org Delivered-To: apmail-flink-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B462187DF for ; Mon, 15 Feb 2016 19:47:40 +0000 (UTC) Received: (qmail 39574 invoked by uid 500); 15 Feb 2016 19:47:40 -0000 Delivered-To: apmail-flink-user-archive@flink.apache.org Received: (qmail 39455 invoked by uid 500); 15 Feb 2016 19:47:39 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 39438 invoked by uid 99); 15 Feb 2016 19:47:39 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Feb 2016 19:47:39 +0000 Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3C52B1A0141; Mon, 15 Feb 2016 19:47:39 +0000 (UTC) Received: by mail-lf0-f47.google.com with SMTP id l143so95427216lfe.2; Mon, 15 Feb 2016 11:47:39 -0800 (PST) X-Gm-Message-State: AG10YOQf+WPOC23H7DM6O8+QCKhhHzqI+6kcruhTGbd6E41bim+1kw2lvsP/XLTb9zDBzsO1HjuVz/JvbG0vdA== X-Received: by 10.25.3.4 with SMTP id 4mr1883274lfd.151.1455565657802; Mon, 15 Feb 2016 11:47:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.190.67 with HTTP; Mon, 15 Feb 2016 11:47:18 -0800 (PST) From: Robert Metzger Date: Mon, 15 Feb 2016 20:47:18 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Flink 1.0.0 Release Candidate 0: Please help testing To: "dev@flink.apache.org" Cc: "user@flink.apache.org" Content-Type: multipart/alternative; boundary=001a113ea0fefb149b052bd449b3 --001a113ea0fefb149b052bd449b3 Content-Type: text/plain; charset=UTF-8 Hi, I've now created a "preview RC" for the upcoming 1.0.0 release. There are still some blocking issues and important pull requests to be merged but nevertheless I would like to start testing Flink for the release. 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 as many issues as possible now with the RC0. Once these issues are resolved, we can start voting with the RC1. 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://people.apache.org/~rmetzger/flink-1.0.0-rc0/ This is the staging repository: https://repository.apache.org/content/repositories/orgapacheflink-1062 To use the release candidate in an existing pom project, set the Flink version to 1.0.0 and the repository URL to https://repository.apache.org/content/repositories/orgapacheflink-1062. The pom should look like this: UTF-8 1.0.0 flink.release-staging Apache Development Snapshot Repository https://repository.apache.org/content/repositories/orgapacheflink-1062 true false Let me start a list of issues we need to resolve: - Ensure the release is build with maven < 3.3 (the RC0 has been build with Maven 3.3, so the Guava shading is not done properly.) - flink-cep depends on Scala, but the artifact doesn't have a scala version suffix. - the flink-quickstart-java is referring to scala 2.11 by default. Please add more issues to the list .... --001a113ea0fefb149b052bd449b3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I've now created a "previe= w RC" for the upcoming 1.0.0 release.
There are still some b= locking issues and important pull requests to be merged but nevertheless I = would like to start testing Flink for the release.

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 pr= ocess by collecting as many issues as possible now with the RC0. Once these= issues are resolved, we can start voting with the RC1.

We have a Wiki page https://cwiki.apache.org/confluence/display/FLINK/Re= leasing containing some common release verification tasks.
Also, production users are encouraged to participate in the re= lease verification process.

Here are the preview b= inaries located:=C2=A0http://people.apache.org/~rmetzger/flink-1.0.0-rc0/
This is the staging repository:=C2=A0https://repository.apache.or= g/content/repositories/orgapacheflink-1062

To use the release candidate in an existing pom project, set th= e Flink version to 1.0.0 and the repository URL to https://reposito= ry.apache.org/content/repositories/orgapacheflink-1062.
The p= om should look like this:

<properties=
>
<project.bu= ild.sourceEncoding= >UTF-8</project.build.sourceEncoding>
<flink.version>1.0.0</flink.version>
</properties>


<repositorie= s>
= <= repository>
<<= span style=3D"color:rgb(0,0,128);font-weight:bold;background-color:rgb(239,= 239,239)">id
>flink.release-staging</id>
<name>Apache Development Snapshot Repository</name>

<url>https://= repository.apache.org/content/repositories/orgapacheflink-1062</url<= span style=3D"background-color:rgb(239,239,239)">>
<releases= ><enabled>= ;true</<= span style=3D"color:rgb(0,0,128);font-weight:bold;background-color:rgb(239,= 239,239)">enabled&= gt;</releases>
<snapshots><enabled>false</enabled></snaps= hots> </repository>
</repositories
>



L= et me start a list of issues we need to resolve:
- Ensure the rel= ease is build with maven < 3.3 (the RC0 has been build with Maven 3.3, s= o the Guava shading is not done properly.)
- flink-cep depends on= Scala, but the artifact doesn't have a scala version suffix.
- the flink-quickstart-java is referring to scala 2.11 by default.
Please add more issues to the list ....




--001a113ea0fefb149b052bd449b3--