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.

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

Update PR Template for LTS Check #26756

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update PR Template for LTS Check #26756

wants to merge 3 commits into from

Conversation

YanaXu
Copy link
Contributor

@YanaXu YanaXu commented Nov 25, 2024

Description

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • For autorest-based development mode, include the changelog in the PR description.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

Copy link

azure-client-tools-bot-prd bot commented Nov 25, 2024

️✔️Az.Accounts
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows

@@ -13,6 +13,8 @@
- [ ] [Engineering build](../blob/main/CONTRIBUTING.md#target-release-types)
- [ ] No need for a release

- [ ] **This needs to be added to LTS version!**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [ ] **This needs to be added to LTS version!**
- [ ] **check this box if this pull request contains fixes for LTS version**

Copy link
Contributor

@NoriZC NoriZC Nov 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should discuss more about how to notify PR authors in a better way.

Simply adding like this may not function as expected. Authors may not understand what is LTS and what should go into LTS version.

@@ -13,6 +13,8 @@
- [ ] [Engineering build](../blob/main/CONTRIBUTING.md#target-release-types)
- [ ] No need for a release

- [ ] **Check this box if this pull request contains fixes for LTS version!**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [ ] **Check this box if this pull request contains fixes for LTS version!**
- [ ] [LTS version](../blob/main/CONTRIBUTING.md#target-release-types).

@BethanyZhou
Copy link
Contributor

Agree with Nori. How about using bug fixes and security fixes to replace the term "LTS". We use this way to describe in our Learn docs

image

@VeryEarly VeryEarly self-assigned this Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants