-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Consolidate info about security releases on the policy page #7658
Conversation
thanks, Jeff! this looks good to me. not sure if the hot fix part needs to be bolded. I did that in the ticket just to clarify the addition but, i'll leave that up to you to keep / remove |
@jeff-matthews oh and one other consideration should we add a link to the policy page? Something like "To read more about our release policy see here" if you think that is not needed then ignore |
Thanks @coreydulimba-ad. If we want to draw attention to that sentence, there's probably a better way to do it (e.g., note format). If not, then no bolding is necessary. |
@jeff-matthews i don't think we need to draw special attention to it, thanks! |
@jeff-matthews and @coreydulimba-ad Do we want to want to change the line to "These releases can also include hotfixes (depending on when these issues are fixed) required to address critical issues that affect the Magento application", to consider the fact that only hotfixes done by code freeze will make it to the patch? Might be confusing but wanted to bring it up. |
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.
Don't use 2.3.5-p2 as an example of a security-only release because we were not able to follow our own patch nomenclature guidelines for 2.3.5. Maybe use 2.3.4 for your example.
Is this one ready? |
Yes, I think so @dobooth. If @coreydulimba-ad and @smiverma want to add additional language later, they can open a PR. |
Hi @jeff-matthews, thank you for your contribution! |
Purpose of this pull request
This pull request (PR) consolidates info about security releases on the policy page.
Affected DevDocs pages