Skip to content

Document our versioning process #3437

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.

Sign up for GitHub

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

Jump to bottom
Closed
2 tasks done
andyleejordan opened this issue Jun 24, 2021 · 0 comments · Fixed by #3431
Closed
2 tasks done

Document our versioning process #3437

andyleejordan opened this issue Jun 24, 2021 · 0 comments · Fixed by #3431
Assignees
@andyleejordan
Labels
Area-Documentation Issue-Enhancement A feature request (enhancement).
Milestone
Committed-vNext

Comments

@andyleejordan
Copy link
Member

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all issues to ensure it has not already been reported.

Summary

I've been inconsistent in choosing version numbers while managing the editor services and our stable and preview channels, therefore I need to pick and document one coherent process so that I can follow it repeatedly.

Proposed Design

No response
@andyleejordan andyleejordan added Issue-Enhancement A feature request (enhancement). Area-Documentation labels Jun 24, 2021
@andyleejordan andyleejordan added this to the Committed-vNext milestone Jun 24, 2021
@andyleejordan andyleejordan self-assigned this Jun 24, 2021
@andyleejordan andyleejordan linked a pull request Jun 24, 2021 that will close this issue
Release refinements #3431
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andyleejordan andyleejordan

Labels
Area-Documentation Issue-Enhancement A feature request (enhancement).
Projects
None yet
Milestone
Committed-vNext
Development

Successfully merging a pull request may close this issue.

Release refinements PowerShell/vscode-powershell
1 participant
@andyleejordan