hey Ismael,
I appreciate you asking questions to make sure we're doing the right things
to help developers out and making sure it's easy to add more IO ITs.
I strongly agree that we need to make sure we have documentation that
clearly lays out how to get it working.
The setup & teardown scripts
thanks for the discussion! In general, I agree with the sentiments
expressed here. I updated
https://docs.google.com/document/d/153J9jPQhMCNi_eBzJfhAg-NprQ7vbf1jNVRgdqeEE8I/edit#heading=h.hlirex1vus1a
to
reflect this discussion. (The plan is still that I will put that on the
website.)
Apache
Hi, Thanks for bringing this subject to the mailing list.
+1
We definitely need a consensus on this, and I agree with your proposal and
JB’s comments modulo certain clarifications:
I think we shall go in this priority order if the version of the image we
want is available:
1. Image provided by
Hi Stephen,
1. About the docker repositories, we now have official Docker repo at Apache.
So, for the Apache projects, I would recommend the Apache official repo. Anyway,
generally speaking, I would recommend the official repo (from the projects).
2. To avoid "unpredictable" breaking change,
hi!
as part of doing the work to enable IO ITs, we decided we want to use
docker. As part of that, we need to run docker images and they'll probably
be pulled from a docker repository.
Questions:
* What docker repositories (and users on docker hub) do we as a group allow
for images we'll run for
