I'd be very happy if we had that integrated into our release process, yes. I'll see how much we can automate there.
> On 15. Dec 2017, at 14:16, Ufuk Celebi <u...@apache.org> wrote: > > 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 > > – Ufuk > > [1] https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release > > On Fri, Dec 15, 2017 at 2:31 AM, Colin Williams > <colin.williams.seat...@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?
