René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Debian future release strategy proposal","articleBody":"- Follows on from https://github.com/nodejs/docker-node/issues/2365\n- Relates to https://github.com/nodejs/docker-node/issues/2397\n\n## Current situation\n\nAccording to the settings in [versions.json](https://github.com/nodejs/docker-node/blob/main/versions.json) every Node.js release line is set to use Debian 12 (bookworm/oldstable) as default, and images are built for each of the Debian major versions: 11 (bullseye/oldoldstable), 12 (bookworm/oldstable) \u0026 13 (trixie/stable) (see [Debian Releases](https://www.debian.org/releases/)).\n\n| Node.js | 11 (bullseye) | 12 (bookworm) | 13 (trixie) |\n| ------- | ------------- | ------------- | ----------- |\n| 20      | used          | default       | used        |\n| 22      | used          | default       | used        |\n| 24      | used          | default       | used        |\n| 25      | used          | default       | used        |\n\n## Suggestion\n\nMake no change for existing release lines Node.js 20, 22, 24 \u0026 25.\n\nFor future release lines starting with Node.js 26:\n\nOn release of a new Node.js release line:\n- package with only the current Debian `stable` release (at the moment this is Debian 13.3 (trixie)), not with earlier Debian major versions\n- set the default Debian version also to the `stable` release\n\nDuring the supported lifetime of a Node.js release line:\n- retain the original Debian major version, add any new major Debian version\n- retain the original default Debian version for the full lifetime of the Node.js release line\n\nThere is no announced date for the release of Debian 14 (forky), however in the past, major [Debian Releases](https://www.debian.org/releases/) have been mid-calendar year every 2 years, so mid 2027 would be a working hypothesis for a possible release date. By this time according to [Node.js release details](https://github.com/nodejs/Release), only Node.js 24 \u0026 26 would still be supported and relevant.\n\n| Node.js | 11 (bullseye) | 12 (bookworm) | 13 (trixie) | 14 (forky)              |\n| ------- | ------------- | ------------- | ----------- | ----------------------- |\n| 20      | used          | default       | used        | N/A EOL                 |\n| 22      | used          | default       | used        | N/A EOL                 |\n| 24      | used          | default       | used        | add when released (TBA) |\n| 25      | used          | default       | used        | N/A EOL                 |\n| 26      | -             | -             | default     | add when released (TBA) |\n\n## Rationale\n\n- According to principles embedded in Node.js release line strategies, support for environments is maintained for the full lifetime of the release line\n- Avoiding packaging of older Debian major versions together with new Node.js release lines reduces the complexity of building, supporting and using Node.js Docker images. This focusses on matching current technology levels together. It also avoids running into the situation where the Debian version is no longer supported where the Node.js release line is still supported. For instance: building Debian 11 (bullseye) with Node.js 24 means that Debian End of LTS on 2026-08-31 occurs before EOL of Node.js 24 on 2028-04-30.\n","author":{"url":"https://github.com/MikeMcC399","@type":"Person","name":"MikeMcC399"},"datePublished":"2026-03-04T11:43:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/2398/docker-node/issues/2398"}