You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2022/04/10 20:20:00 UTC
[jira] [Comment Edited] (GUACAMOLE-1552) Add "dev" docker images targetting master github branch
[ https://issues.apache.org/jira/browse/GUACAMOLE-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520220#comment-17520220 ]
Mike Jumper edited comment on GUACAMOLE-1552 at 4/10/22 8:19 PM:
-----------------------------------------------------------------
The release distribution policy says that unreleased materials (such as a nightly build or dev build) must not be published outside the development community. Only releases can be published for general consumption. From [https://www.apache.org/legal/release-policy.html#publication]:
{quote}
Projects SHALL publish official releases and SHALL NOT publish unreleased materials outside the development community. ... Projects SHOULD make available developer resources to support individuals actively participating in development or following the dev list and thus aware of the conditions placed on unreleased materials.
{quote}
As long as we are _very_ conspicuous in the way these images are marked, there's no potential for a normal user to accidentally pull a dev image, and we do not link to these images nor encourage their use except on dev@ and dev-specific parts of the website, I believe we should be OK. For example, we could build {{guacamole/guacamole-dev}} and {{guacamole/guacd-dev}} (or {{-nightly}}? {{-snapshot}}?), and include a specific note in the image overviews on Docker Hub that these images are not releases and are intended for development testing only, etc. Including a link to the dev images on the main download page or on user@, on the other hand, would definitely be against policy.
was (Author: mike.jumper):
The release distribution policy says that unreleased materials (such as a nightly build or dev build) must not be published outside the development community. Only releases can be published for general consumption. From https://www.apache.org/legal/release-policy.html#publication:
{quote}
Projects SHALL publish official releases and SHALL NOT publish unreleased materials outside the development community. ... Projects SHOULD make available developer resources to support individuals actively participating in development or following the dev list and thus aware of the conditions placed on unreleased materials.
{quote}
As long as we are _very_ conspicuous in the way these images are marked, there's no potential for a normal user to accidentally pull a dev image, and we do not link to these images nor encourage their use except on dev@ and dev-specific parts of the website, I believe we should be OK. For example, we could build {{guacamole/guacamole-dev}} and {{guacamole/guacd-dev}} (or {{-nightly}}? {{-snapshot}}?), and include a specific note in the image overviews on Docker Hub that these images are not releases and are intended for development testing only, etc. Including a link to the dev images on the main download page or on user@, on the other hand, would definitely be against policy.
> Add "dev" docker images targetting master github branch
> -------------------------------------------------------
>
> Key: GUACAMOLE-1552
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1552
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker, guacd-docker
> Affects Versions: 1.4.0
> Reporter: Jean-Benoit PAUX
> Priority: Minor
> Labels: Docker
>
> Current Docker Hub images include images tagged with their respective guacamole tags (1.3.0, 1.4.0...) and latest build with latest released guacamole version (1.4.0 currently) on top of latest vendor base images on a daily basis.
> It would be great if automatic nightly build could create "dev" docker images with github master branch sources so we can easily test latest improvements.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)