Skip to content

Decide on what to do with Node version in dockerization guide. #2988

Closed as not planned
@mkrawczuk

Description

@mkrawczuk

Currently, an old version of LTS Node is mentioned in the guide. A fix has been proposed in PR #2953, and shortly after, #2983 followed. I'm opening this issue to avoid splitting the discussion between these two PRs.

The former lets the maintainers forget about manual version bumping which may be a source of inaccuracies (as proven in PR description), but may cause problems to the users, since the version is variable and changes with new Node releases.

The latter is safer for the users, but may again cause inaccuracies, also requires manual version bump with every LTS release. It also requires to add another point to an already long list in the release process.

I would personally go with the former. Only advantage of #2983 over #2953 is that it might protect the user from some discrepancies in case of a new Node LTS release. However I believe that problems emering from such discrepancies are very improbable. Additionally, even the best guide will not prevent from misuse of software.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions