-
Notifications
You must be signed in to change notification settings - Fork 621
Add extra sentence about testing core first #2619
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
base: devel
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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?
|
||
|
||
Playbook | ||
======== | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be a good idea to show an example of how people can "install" stable-2.19?