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

Review EngHub for verbiage discrepencies #9843

Open
jrferry101 opened this issue Feb 15, 2025 · 0 comments
Open

Review EngHub for verbiage discrepencies #9843

jrferry101 opened this issue Feb 15, 2025 · 0 comments
Assignees
@jrferry101
Labels
Engagement Experience

Comments

@jrferry101
Copy link

We need to refine the terminology used in our Release Planner and EngHub to better align with the way our development teams think about SDKs and services. Specifically, we should avoid using the term "Product" and instead focus on "Versions" of services and SDK packages. This will help ensure clarity and consistency across our documentation and planning tools.

See this message thread:
https://teams.microsoft.com/l/message/19:meeting_YTIwNGUzYjEtNzMxMC00OTkzLWE4NWYtNTY3MzNhYjQyOGYz@thread.v2/1739579485678?context=%7B%22contextType%22%3A%22chat%22%7D
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Feb 15, 2025
@MrJustinB MrJustinB moved this from New to Backlog in Engagement Experience Feb 15, 2025
@MrJustinB MrJustinB added Engagement Experience and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jrferry101 jrferry101

Labels
Engagement Experience
Projects
Engagement Experience
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MrJustinB @jrferry101