Hi Israel, short answer: I'm not a big fan of starting the release process for a 2 commit branch. We would need to do the vote, wait 72 hours and all the other "paperwork".
That being said, Dockerhub is not an official release channel so I can create an image containing those 2 commits and freeze it for you until we have everything sorted out in 2.1, then you can refer to this custom image for your blogpost. Our 2.1-SNAPSHOT however should not have drifted off from 2.0 that far yet, so I am also interested in what is going on. Do you get any feedback in the log/browser or does the UI just not load? Then we can create a ticket to definitely get this sorted out before we start our next release. Kr, Hans On Wed, 22 Jun 2022 at 18:52, Israel Herraiz <[email protected]> wrote: > Hi, > > TL;DR: I am working on a blog post on using the Hop web container with > Cloud Dataflow, and having a "2.0.1" release of the Docker container would > help with that post. > > Using the 2.0 Docker container of Hop web I found a couple of small issues > that prevented me from being able to use Cloud Dataflow with that container > image (HOP-3976 <https://github.com/apache/hop/pull/1523>, HOP-3977 > <https://github.com/apache/hop/pull/1524>). > > If I try with the 2.1-SNAPSHOT container, I have other problems (the main > UI does not load), and I cannot use Hop with Cloud Dataflow either. > > I cherry-picked the commits of those pull requests linked above, applied > them on top of the release2.0.0 branch > <https://github.com/apache/hop/tree/release2.0.0>, and produced a custom > container, and it works fine. But I think that asking the blog post readers > to do a custom container will be too much (I want to focus on how easy is > to use Hop from a web browser :). > > Would it be possible to have a "2.0.1" container released with those > commits so I can link it as the image to be used with my blog post? > > Thanks. > > Israel >
