2024-06-07, 12:45 AM
Hi Joshua, I really appreciate the work that you and all the other members of the team do on this project.
This:
Just broke my (and no doubt others) update script.
If I could offer some commentary, please consider putting the keyword in the tag name.
So you wouldn't just have X, you'd have X-MAJOR, or even just MAJOR.
Anyone tracking MAJOR likely doesn't care about it being X, only that it's always going to have the latest MAJOR in it.
If _I_ was doing the naming, I'd do this:
latest
major
minor
point
nightly-YYYYMMDD-HHMMSS
X.Y.Z
Everybody wins, and it's obvious what each one is.
This:
(2024-06-06, 07:26 PM)joshuaboniface Wrote: For our Docker users, we now have additional tags you can use to more granularly pull the images! This applies both to Docker Hub and GHCR. Going forward, we'll be publishing tags like so:
latest, always tracks whatever the latest release is, including through major and minor version bumps
X(e.g. 10), tracks the latest in 10.y.z (which is our "major" version for the forseeable future) NEW
X.Y(e.g. 10.9), tracks the latest in 10.9.z minor, good for those who don't want to jump right to 10.10 later on but want the bugfix releases automatically NEW
X.Y.Z(e.g. 10.9.6), tracks the specific point release
X.Y.Z.YYYYMMDD-HHMMSS(e.g. 10.9.6.20240606-184155), tracks the specific packaging build, which in future might change for long-running stable releases to update dependencies and such, while still tracking the same Jellyfin code revision (i.e.vX.Y.Ztag)
Just broke my (and no doubt others) update script.
If I could offer some commentary, please consider putting the keyword in the tag name.
So you wouldn't just have X, you'd have X-MAJOR, or even just MAJOR.
Anyone tracking MAJOR likely doesn't care about it being X, only that it's always going to have the latest MAJOR in it.
If _I_ was doing the naming, I'd do this:
latest
major
minor
point
nightly-YYYYMMDD-HHMMSS
X.Y.Z
Everybody wins, and it's obvious what each one is.