Why not versioning the dotnet-install scripts?

Open
#580 1 comment 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
powershell
Domain
tooling

Research direction

Start by reading the dotnet-install scripts and the related issue #121 to understand the current distribution and update flow. Define how releases, semantic-version changes, package-manager use, and local-versus-newest checks should work; the work is done when the versioning approach is specified and implemented consistently.

Written by the indexing model from the issue text.

Description

needs-pm-discussion

It'd be beneficial to version the dotnet-install scripts, as in make actual releases of them.

  • Make it easier to manage it with package managers.
  • Compare local version vs. newest version, instead of re-downloading the whole script to be sure one is up to date.
  • Signal minor vs major/braking changes, following semantic versioning.
  • And other benefits of having something versioned.

Somewhat related:

  • #121
Dominant language
PowerShell
Stars
213
Forks
120
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/install-scripts

All issues in dotnet/install-scripts

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.