Skip to content

Add opt-prof expiration data extension step to the release checklist #12075

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AR-May
Copy link
Member

@AR-May AR-May commented Jun 26, 2025

We need to preserve one opt-prof data for every release branch that is in support. We should always have some opt-prof in VS Drop that we can use for the servicing if needed. Add an action to the release check list for preserving the opt-prof data.

@AR-May AR-May force-pushed the update-release-checklist-4 branch from 14f037c to 4f2e79b Compare June 26, 2025 12:15
@AR-May AR-May marked this pull request as ready for review June 26, 2025 12:16
@Copilot Copilot AI review requested due to automatic review settings June 26, 2025 12:16
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Adds a step to the release checklist for preserving Opt-Prof data by extending its expiration in the VS Drop for servicing support.

  • Introduces a new checkbox for extending Opt-Prof data expiration.
  • Details how to locate the latest Opt-Prof drop, acquire the drop.exe tool, and apply the extension.
Comments suppressed due to low confidence (2)

documentation/release-checklist.md:137

  • Add an example drop.exe command snippet showing how to update the expiration (e.g., drop update-expiration --id <drop-id> --expiration <YYYY-MM-DD>), so the manual step is clearer.
  - Use [this instruction](https://dev.azure.com/devdiv/DevDiv/_wiki/wikis/DevDiv.wiki/30808/Extend-a-drop's-expiration-date) to set the new expiration to (End of support date for the corresponding Visual Studio version) plus 3 months.

documentation/release-checklist.md:137

  • Link to the official Visual Studio lifecycle page or a maintained reference so that the source of the "End of support date" is clear and stays up to date.
  - Use [this instruction](https://dev.azure.com/devdiv/DevDiv/_wiki/wikis/DevDiv.wiki/30808/Extend-a-drop's-expiration-date) to set the new expiration to (End of support date for the corresponding Visual Studio version) plus 3 months.

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.

3 participants