incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <>
Subject Re: Namespacing of subproject Docker images vs. Incubator policy
Date Wed, 07 Sep 2016 00:38:06 GMT
On Thu, Sep 1, 2016 at 7:47 PM, Mike Jumper <> wrote:

> All, setting aside the Docker Hub vs. Apache-hosted hub vs. bintray
> discussion for the moment,

The issue of* has been worked out in principle with
Infra.  Only official releases will be be built, and `latest` will point to
an image based on the last official release.  The plan has not yet been
implemented, but now you know what to expect in the future.

See the infrastructure@apache thread (login required):

> are there any specific opinions regarding
> the original issue: the actual namespacing of the podling images
> themselves?

>     apache/incubator-guacamole:0.9.10-incubating
>     apache/incubator-guacd:0.9.10-incubating

Using how we name Git repos as precedent, the image address would be:


... and with tags:


>     - Seems redundant (incubator, incubating), graduation would break
>       compatibility (see Maven best practices [1])

I agree that it would be best not to break compat on graduation.

>     apache/guacamole:0.9.10-incubating
>     apache/guacd:0.9.10-incubating

Or, matching up with our (post-graduation) Git repo naming
convention again:



I think this is best.  However, it bugs me that users are not provided with
adequate disclaimers for the common case that fetches `latest` as the default

    docker pull apache/guacamole

I don't have any ideas beyond requiring a prominent incubation disclaimer on
the repo info page at$REPO/ .

Marvin Humphrey

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message