Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rolling tags for upstream stable tracking #2265

Open
joshtrichards opened this issue Jul 18, 2024 · 3 comments
Open

Rolling tags for upstream stable tracking #2265

joshtrichards opened this issue Jul 18, 2024 · 3 comments
Labels
0. Needs triage image meta Things about the repo itself

Comments

@joshtrichards
Copy link
Member

joshtrichards commented Jul 18, 2024

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)
@khassad
Copy link

khassad commented Jul 21, 2024

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 ?

@joshtrichards
Copy link
Member Author

joshtrichards commented Jul 22, 2024

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

@khassad
Copy link

khassad commented Jul 22, 2024

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 #2269

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage image meta Things about the repo itself
Projects
None yet
Development

No branches or pull requests

2 participants