Canonical tool versions in different execution environments: Declaration + Documentation

(1) As a developer in the team pulling a new version of the dev branch, I want my machine to automatically bump my tools to the right version So that I don't need to upgrade manually

(2) As a developer in the team merging an upgrade, I want to set the version of any tool that is required for the build to succeed at a single location So that the version of a tool declared in one config file never diverges from other declarations

(3) As an onboarding developer in the team, I want my environment to be prepared for (1) and (2) So that I never struggle with out-of-sync tool version

(4) As a developer in the team, I need a documentation that clearly states how the dev and build processes use and install tools So that I know how the development tools interact with my machine and my userspace configuration (nvm, node,...)

-

  • Declarative configuration for environments
    There is a declarative configuration per environment to manage the versions of all tools in the stack.
  • Single source of Software versions per environment
    The environments are configured in such a way that there is only one place where we bump version numbers.
  • Features are documented
    The configuration of tool versions is documented in the README and/or CONTRIBUTING document. #36

-

Also see #19 (closed)

Also see #17 (closed)

Edited by Jon Richter