You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
On the surface this seems like an easy one, but this is an oddball because it's also equivalent to not specifying any label at all and therefore the Docker default. Since it's the de facto entry point for newcomers, it is reasonably debatable whether starting people on the most bleeding edge is always ideal.
Outside of the Apache/default, latest is also a modified for the other image types (fpm, alpine) in the same manner
production is just a mirror of stable.
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)
The text was updated successfully, but these errors were encountered:
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 ?
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)The text was updated successfully, but these errors were encountered: