Open joshtrichards opened 4 months ago
Hello, I don't get it since the tracking url you reference for stable has 28.0.8 since 3 days ago but I don't see any hint of this release being in the release pipeline for the docker image. How can we get a predictable timeline of docker images of new releases ?
WIP: #2269
In this issue I'm mostly focusing on documenting more formally what we currently do (or try to do) as well as couple potential refinements.
How can we get a predictable timeline of docker images of new releases ?
By putting in the work as a community to make that happen.
P.S. A new release of the image set with bumps to 28.0.8 / 29.0.4 is pending over in the docker-library/official-images#17220
Thanks for the answer, I landed on this issue and had hopes to get a view of the release process. I will try and follow up in https://github.com/nextcloud/docker/issues/2269
Goal: Track official upstream designations for the various non-EoL majors at any given point in time
Existing but better document:
stable
always point to the highest numbered of the currently supported majors (e.g 27, 28, 29) that is published to 100% of instances via the Nextcloud Update Server.latest
always points at the absolute highest of the currently supported majors without regard for 100% general availability.latest
is also a modified for the other image types (fpm, alpine) in the same mannerproduction
is just a mirror ofstable
.New (proposed not actually implemented):
previous
is the most recent major behind the latest major which is receiving regular bug fixes.last
is the oldest major still receiving updates.Related:
{major}-{apache, fpm}
(e.g.28-apache
) always points to the latest published maintenance release for the specified major*-alpine
variations in all cases where applicable (no need for debian/bookworm since that's our default base)