Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <CAPXXXSBvsUgt8Vw2zuc-ONN7X08-sPdZgRDs_FKvzhpAuni=9A@mail.gmail.com>
References: <CAPXXXSBvsUgt8Vw2zuc-ONN7X08-sPdZgRDs_FKvzhpAuni=9A@mail.gmail.com>
From: Ufuk Celebi <uce@apache.org>
Date: Fri, 15 Dec 2017 14:16:48 +0100
Message-ID: <CAKiyyaEs1D9uWJS1kiFey2W2u7rJsL1uLoSwvfLd9WOteMOExQ@mail.gmail.com>
Subject: Re: docker-flink images and CI
To: Colin Williams <colin.williams.seattle@gmail.com>
Cc: user <user@flink.apache.org>, Patrick Lucas <patrick@data-artisans.com>,
	Aljoscha Krettek <aljoscha@apache.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 15 Dec 2017 13:17:35 -0000

I agree with Patrick's (cc'd) comment from the linked issue. What I
understand from the linked issue is that Patrick will take care of the
Docker image update for 1.4 manually. Is that ok with you Patrick? :-)

Regarding the Flink release process question: I fully agree with the
idea to integrate this into the release process. As it stands the
Flink release process is pretty manual though [1]... Let me include
the release manager of the 1.4 release Aljoscha (cc'd) to get his
opinion on the issue.

In any case, I'm in favour of this. +1

=E2=80=93 Ufuk

[1] https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Rele=
ase

On Fri, Dec 15, 2017 at 2:31 AM, Colin Williams
<colin.williams.seattle@gmail.com> wrote:
> I created the following issue on here:
> https://github.com/docker-flink/docker-flink/issues/29 where it was
> suggested I should bring this up on the list.
>
> 1.4 has been released. Hurray!
>
> But there isn't yet a dockerfile / image for the release. Furthermore, it
> would be nice to have dockerfile / images for each RC release, so people =
can
> incrementally test features using docker before release.
>
> Is it possible to use CI to generate images and add Dockerfiles for each
> release?