[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788009#comment-17788009
 ] 

Nick Couchman edited comment on GUACAMOLE-1884 at 11/20/23 1:32 PM:
--------------------------------------------------------------------

First, please post questions to the mailing list, not to Jira - this is not a 
discussion/support forum.

The "latest" Docker images are rebuilt daily with updates to the underlying O/S 
packages, even if the Guacamole version does not change, which is likely why 
you're seeing the "daily" upload/update to the Docker image.


was (Author: nick.couch...@yahoo.com):
First, please post questions to the mailing list, not to Jira - this is not a 
discussion/support forum.

The Docker images are rebuilt daily with updates to the underlying O/S 
packages, even if the Guacamole version does not change, which is likely why 
you're seeing the "daily" upload/update to the Docker image.

> Why is "latest" docker release constantly re-uploaded?
> ------------------------------------------------------
>
>                 Key: GUACAMOLE-1884
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1884
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-docker, guacd-docker
>            Reporter: Fernando ViƱan-Cano
>            Priority: Trivial
>              Labels: docker
>         Attachments: image-2023-11-20-14-15-16-046.png
>
>
> I noticed that both guacamole-docker and guacd-docker latest are 
> rebuilt/pushed so often that they appear like they are new releases.
> As far as I am aware they are all v1.53 so the last pushed should be 4 months 
> ago not 11hrs as I see right now - conversely the -dev releases seem to be 
> much longer between releases and probably matches real dev releases.
> If they are newer, shouldn't they either be properly released with a new 
> version number, or pushed to the -dev ones?
> !image-2023-11-20-14-15-16-046.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to