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

Document Policy for Supporting Compilers/Runtimes #103

Closed
RobbieMcKinstry opened this issue Aug 12, 2022 · 1 comment
Closed

Document Policy for Supporting Compilers/Runtimes #103

RobbieMcKinstry opened this issue Aug 12, 2022 · 1 comment
Assignees
Labels
area/build kind/enhancement Improvements or new features resolution/fixed This issue was fixed size/S Estimated effort to complete (1-2 days).

Comments

@RobbieMcKinstry
Copy link
Contributor

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

This repository offers container images for all of our supported languages. However, we don't provide documentation of what version of the language is installed on the container image.

We want customers to know our policy for upgrading the compilers/runtimes associated with each language.
This has two primary benefits:

  1. It allows customers who rely on these images but run old versions of the language to know how much time they have to upgrade. For example, support a customer is running Go 1.18. They may want to know when we plan to bump the version of this Go image from 1.18 to 1.19 so they can prepare their source code to be compatible with 1.19. In the case of Go, this isn't too much of a problem since the Go compatibility promise guarantees straightforward upgrading. However, for languages like NodeJS, this is not the case.

  2. It establishes a timeline for us to upgrade the container images. We want to know when we can upgrade the images without breaking our customers' programs.

As an ancillary benefit, documenting the upgrade policy increases our accountability. Right now, container images seem to be inconsistently upgraded across languages. For example, the Go version is pinned to 1.18, but our NodeJS runtime floats to whatever is LTS.

You can see we won't specify the language version in our Dockerhub documentation (Go, for example).

Affected area/feature

  • Dockerhub Documentation
  • The Dockerfile ARGs themselves
  • This repo's README
@RobbieMcKinstry RobbieMcKinstry added kind/enhancement Improvements or new features size/S Estimated effort to complete (1-2 days). area/build labels Aug 12, 2022
@RobbieMcKinstry RobbieMcKinstry added this to the 0.77 milestone Aug 21, 2022
@RobbieMcKinstry RobbieMcKinstry self-assigned this Aug 21, 2022
@RobbieMcKinstry RobbieMcKinstry linked a pull request Aug 21, 2022 that will close this issue
5 tasks
@RobbieMcKinstry RobbieMcKinstry modified the milestones: 0.77, 0.78 Sep 3, 2022
@mikhailshilkov mikhailshilkov removed this from the 0.78 milestone Sep 6, 2022
@julienp julienp self-assigned this Oct 31, 2024
@julienp julienp added the resolution/fixed This issue was fixed label Oct 31, 2024
@julienp
Copy link
Contributor

julienp commented Oct 31, 2024

@julienp julienp closed this as completed Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build kind/enhancement Improvements or new features resolution/fixed This issue was fixed size/S Estimated effort to complete (1-2 days).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants