Add branch messaging across respective files #2248
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
This PR adds messaging to changelogs and readmes to alert folks to the pending change, currently listed as coming in the 3.7.0 release, of removing built assets from
develop
, building into astable
branch, and removingmaster
in favor oftrunk
and removing built assets fromtrunk
.This PR only attempts to cover the first checkbox here: #2182 (comment). We'll want to mirror this messaging across future 3.6.* releases to continue communicating these pending changes. We'll also need to work through the additional checkboxes on #2181, happy to help with more there as desired.
Alternate Designs
Potentially adding messaging into other places across the codebase, or adjusting copy to be more precise.
Benefits
Ensures we attempt to alert as broad a base of users as possible ahead of making these changes.
Possible Drawbacks
None identified besides over communicating.
Verification Process
Verified via VS Code and GitHub Desktop UI.
Checklist:
Applicable Issues
Relates to #2182.
Changelog Entry