Skip to content

Commit

Permalink
Announce deprecation changes
Browse files Browse the repository at this point in the history
  • Loading branch information
thespad committed Aug 11, 2024
1 parent 8219be2 commit c5371aa
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions content/issues/2024-08-11-deprecation-changes.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
title: 'Changes To Our Image Deprecation Process'
date: '2024-08-12 18:00:00Z'
informational: true
affected:
- Deprecations
section: issue
---

Currently, when we deprecate an image, we add a note to the readme and to the startup logs to make users aware that the image is no longer actively supported and will not receive further updates. Users can then make their own decision as to whether to continue using it or not. Despite this, we still see a significant number of pulls for images that we have long since stopped updating, primarily because users don't read the notices, or use a container management platform that doesn't expose them.

Wherever possible we want to avoid actually removing images from registries, because it can prevent legitimate uses of them & because we feel it goes against the open source philosophy, so to try and reduce the number of users setting up new instances with unsupported and outdated images, we are changing our deprecation process.

Going forward, when we deprecate an image, we will be pushing an empty index for the `latest` tags (or corresponding branch tags for alternate releases such as develop or nightly). This will make it impossible for someone to pull the `latest` tag for that image and require them to specifically identify and pull a named version tag. Our hope is that by adding this small hurdle it will dramatically reduce the number of users unknowingly running unsupported images.

0 comments on commit c5371aa

Please sign in to comment.