Plugin-Testing List 1.14.0 documentation #954
Draft
+6,925
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rainkwan
changed the title
Vercel Previews Deployed
|
rainkwan
force-pushed
the
rk/plugin-testing-1-14-0
branch
from
e4a1bb6 to
6a51921
Compare
Broken Link CheckerNo broken links found! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Terraform Enterprise
Contributor Sign Off
Congratulations, if your name is on this list that means you contributed to this release. You must sign off on your
contributions by checking the box in front of your username. The number in front of your username is the number of pull
requests authored by you that are going into this release.
Please review the changelog entries for your contributions. Your changelog entries should be feature-focused, define
the what and why, and include any necessary information for customers. Each changelog entry should make it clear
why the customer should care about the change. More information on
how to write release notes can be found in confluence.
Place your changelog entry into one of the following categories.
Known Issues: Issues present in this release. Ideally each issue will describe a workaround or provide information
on which release resolves the issue. This category is typically added after a release is published.
Breaking Changes: Changes that will require a customer to take some action to modify their workflow, processes,
monitoring, etc.
Deprecations: Things that will no longer be supported by the application. Can be operating systems going
end-of-life, settings being removed, etc.
Highlights: Noteworthy changes that the customer should see when reading the release notes. These should be
approved by your Product Manager and/or Engineering Manager.
Features: Newly added functionality to the application.
Improvements: Updates to existing components of the application.
Bug Fixes: Fixes to issues reported with the application.
Security: Security enhancements to the application and its infrastructure and patches for Common Vulnerabilities
and Exposures (CVEs).
When you are finished reviewing your contributions, check the box next to your name.
Please let @hashicorp/technical-program-mgmt know if you have any questions.