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 03E2C18ABA for ; Wed, 3 Feb 2016 09:38:41 +0000 (UTC) Received: (qmail 9922 invoked by uid 500); 3 Feb 2016 09:38:40 -0000 Delivered-To: apmail-flink-user-archive@flink.apache.org Received: (qmail 9844 invoked by uid 500); 3 Feb 2016 09:38:40 -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 9466 invoked by uid 99); 3 Feb 2016 09:38:40 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Feb 2016 09:38:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id F3DC81A0424 for ; Wed, 3 Feb 2016 09:38:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Qo9cY-ckEM6E for ; Wed, 3 Feb 2016 09:38:37 +0000 (UTC) Received: from mail-lb0-f178.google.com (mail-lb0-f178.google.com [209.85.217.178]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id E5FA920CD0 for ; Wed, 3 Feb 2016 09:38:36 +0000 (UTC) Received: by mail-lb0-f178.google.com with SMTP id bc4so8514375lbc.2 for ; Wed, 03 Feb 2016 01:38:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=YYUCT8F0rkPxYaAOMyC0yd6Fmapp6avVL9M4ozTvGJw=; b=CouGa93JAsRPyfYx+i3uXyuYHJ+8xtZau+zkRf1tEznuqGs3Jf3VPRa1avYDGVNC8v Xfb9esteZPGKS/g7PVNJKuKT6NPz3a7qly+JFgjtTeCpWwm75aIPw6neXV+jJEc/fzbb qrE0OLYhvYWjXuzwwuZuf9NOEc5LaMeLWGaQxlwt123YpUMH3rJxEyUPQaaFtj/wVBUG ZdvHsrtxytqgExGR26B8S99qSJJkZ/rVhU43tIGhgJIxQxb+EeHtaNkYJuSLewuf1JOF yt8bUDVeJQfBnLcB4jClHq5w2HmEqvXBiiuKAftQVDi7DRSIvN6Dys5xqOm75OBn1k0e FG2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=YYUCT8F0rkPxYaAOMyC0yd6Fmapp6avVL9M4ozTvGJw=; b=bfc/8PrUofQHzfkoYEh9oQQHTcitSmLyxpTMsPTq3POIA7uglWkEGbnO9y8gcAuqDq +RYL/v8KMQDLf98W/obBWipcKheDoDQ4oOxtd8e+L1vLqvPBpV+5QahS9wCsv9zsMilP xO2x6ZveUzpO8ep+9TK6S66UakTAabirAyEXp0Srt46tcsR1H0CI73qD5w++HSJjhRaq +x2ugmCzSL+iwfVwpx0fIp4jr/E1k43uBDQeEe97G74dDurZxDIu5CXbARSocL8Q/Yll 6jtZuuna3Son1Qt40UcbdmVGqFX7sORTf1UrZ9WhFpz5IkxVhGK6pEFwqSAUMThlptak UhUQ== X-Gm-Message-State: AG10YORZ9m6aDpD/nA6NDM6cuWA4JY/sexlIZs6C2nIMRgE92cvYfVFtTon8rJErnXEnPjX20vY+AJDKUyDPrg== X-Received: by 10.112.144.226 with SMTP id sp2mr276230lbb.70.1454492315115; Wed, 03 Feb 2016 01:38:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.161.198 with HTTP; Wed, 3 Feb 2016 01:38:05 -0800 (PST) In-Reply-To: References: From: Fabian Hueske Date: Wed, 3 Feb 2016 10:38:05 +0100 Message-ID: Subject: Re: Build Flink for a specific tag To: user@flink.apache.org Content-Type: multipart/alternative; boundary=047d7b342fd4c56555052ada6125 --047d7b342fd4c56555052ada6125 Content-Type: text/plain; charset=UTF-8 Hi Flavio, we use tags to identify releases. The "release-0.10.1" tag, refers to the code that has been released as Flink 0.10.1. The "release-0.10" branch is used to develop 0.10 releases. Currently, it contains Flink 0.10.1 and additionally a few more bug fix commits. We will fork off this branch to release Flink 0.10.2 in a few days. So, if you would like to compile Flink 0.10.1 you should use the tag. If you would like to have Flink 0.10.1 with the latest bug fixes, you should compile the release-0.10 branch. Cheers, Fabian 2016-02-03 10:31 GMT+01:00 Flavio Pompermaier : > Is it sufficient to do *git checkout tags/release-0.10.0 *and the > compile it? > However I think it's worth to mention this in the build section of the > documentation.. > > Best, > Flavio > > On Wed, Feb 3, 2016 at 9:57 AM, Flavio Pompermaier > wrote: > >> Hi to all, >> >> I wanted to update my Flink cluster installation to Flink 0.10.1 but I >> can't find the respective branch. >> In the past, I used to go in the apache-flink git folder, exec a *git >> pull *and a *git branches -a* in order to *checkout* on the proper >> release branch. However I saw that there's only a tag for the 0.10.1 >> release (i.e. release-0.10.0). What command should I do to align my sources >> with that tag? >> >> Also in the documentation ( >> https://ci.apache.org/projects/flink/flink-docs-master/setup/building.html) >> there's no mention on how to build Flink for a specific tag :( >> >> Thanks in advance, >> Flavio >> > > > --047d7b342fd4c56555052ada6125 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Flavio,

we use ta= gs to identify releases. The "release-0.10.1" tag, refers to the = code that has been released as Flink 0.10.1.
The "release-0.1= 0" branch is used to develop 0.10 releases. Currently, it contains Fli= nk 0.10.1 and additionally a few more bug fix commits. We will fork off thi= s branch to release Flink 0.10.2 in a few days.

So, if you wou= ld like to compile Flink 0.10.1 you should use the tag.
If you wou= ld like to have Flink 0.10.1 with the latest bug fixes, you should compile = the release-0.10 branch.

Cheers, Fabian

2016-02-03 10:31 GMT+01:00 Fla= vio Pompermaier <pompermaier@okkam.it>:
Is it sufficient to do=C2=A0=C2=A0git = checkout tags/release-0.10.0 and the compile it?
However I think it= 's worth to mention this in the build section of the documentation..

Best,
Flavio

On Wed, Feb 3,= 2016 at 9:57 AM, Flavio Pompermaier <pompermaier@okkam.it> wrote:
Hi to all,

I wanted to update my Flink cluster installation to Flink 0.10.1 but I= can't find the respective branch.
In the past, I used to go = in the apache-flink git folder, exec a git pull and a git branche= s -a in order to checkout on the proper release branch. However = I saw that there's only a tag for the 0.10.1 release (i.e. release-0.10= .0). What command should I do to align my sources with that tag?
=
Also in the documentation (htt= ps://ci.apache.org/projects/flink/flink-docs-master/setup/building.html= ) there's no mention on how to build Flink for a specific tag :(
<= div>
Thanks in advance,
Flavio=C2=A0


<= p>


--047d7b342fd4c56555052ada6125--