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.

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

Rename released module to Microsoft.PowerShell.PSReadline for next major version #3787

Open
1 task done
kilasuit opened this issue Aug 21, 2023 · 2 comments
Open
1 task done

Rename released module to Microsoft.PowerShell.PSReadline for next major version #3787

kilasuit opened this issue Aug 21, 2023 · 2 comments
Labels
Issue-Enhancement It's a feature request.
Milestone
Future

Comments

@kilasuit
Copy link

kilasuit commented Aug 21, 2023 •
edited

Prerequisites

  • Write a descriptive title.

Description of the new feature/enhancement

This is something that is happening with other modules that started out as non-team work and have then jumped into the product, including PSResourceGet, ThreadJob and others.

This is to align with that expectation

cc @daxian-dbw @StevenBucher98

Proposed technical implementation details (optional)

No response
@kilasuit kilasuit added the Issue-Enhancement It's a feature request. label Aug 21, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage 🔍 It's a new issue that core contributor team needs to triage. label Aug 21, 2023
@daxian-dbw
Copy link
Member

I don't think this is needed for 2.3 release. PowerShell has the built-in modules like "CimCmdlets" and "PSDiagnostics", and I don't think they will be renamed any time soon.

@kilasuit
Copy link
Author

I was thinking more for a 3.0 release so that it has plenty of time to be communicated if it's decided that this is something that we want to ensure of consistency or not.

@StevenBucher98 StevenBucher98 removed the Needs-Triage 🔍 It's a new issue that core contributor team needs to triage. label Aug 21, 2023
@StevenBucher98 StevenBucher98 added this to the Future milestone Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Enhancement It's a feature request.
Projects
None yet
Milestone
Future
Development

No branches or pull requests
3 participants
@daxian-dbw @kilasuit @StevenBucher98