Add extra sentence about testing core first #2619
Open
+1
−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
samccann
added
techreview
jborean93
reviewed
May 8, 2025
| @@ -29,6 +29,7 @@ with wide-ranging positive effects on security, performance, and user experience | |||
| Backward compatibility has been preserved where practical, but some breaking changes were necessary. | |||
| This guide describes some common problem scenarios with example content, error messsages, and suggested solutions. | |||
|
|
|||
| We recommend you test your playbooks and roles in a staging environment with stable-2.19 to determine where you may need to make changes. | |||
There was a problem hiding this comment.
It might be a good idea to show an example of how people can "install" stable-2.19?
mattclay
reviewed
May 8, 2025
| @@ -29,6 +29,7 @@ with wide-ranging positive effects on security, performance, and user experience | |||
| Backward compatibility has been preserved where practical, but some breaking changes were necessary. | |||
| This guide describes some common problem scenarios with example content, error messsages, and suggested solutions. | |||
|
|
|||
| We recommend you test your playbooks and roles in a staging environment with stable-2.19 to determine where you may need to make changes. | |||
There was a problem hiding this comment.
We should probably leave it up to users how they're going to acquire 2.19 for testing, rather than mentioning the stable branch, or even repeating the version number. How about something like this?
We recommend you test your playbooks and roles in a staging environment with this release to determine where you may need to make changes.
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.
Based on idea from forum post.