Changes to plugins(Upgrade)

[Ereshkigal]

Hi.

Along with the Tokyo release, we are confirming the upgrade work. I think there is a document called "Changes to Plugins" in the release notes.

This is the confirmation method, but I'm trying to check it by the following procedure, Is there any problem?

1. Check if the "Combined product release notes" mention the plugin
2. If there is a description of the plugin, check what kind of updates have been made to the plugin itself in the "Changes to Plugins"
3. Check if the plugin is active on the instance
4. Check if activated plugins affect customization and overall operation
5. If so, consider additional customization or deactivation of plugins

Also, as an additional confirmation, instead of checking the "Changes to Plugins" one by one, If there is a description in the "Combined product release notes", I think it would be good to check it, What do you think. (Because they often don't provide much detail.)

[Mark Manders]

Looks like you got everything covered and yes, any 'combined product release notes' should always be checked. Even if you just have 1 line saying 'don't forget to do this with that property' or something like that: it could make hours of difference to check it. 

But from the upgrade perspective: focus on what to do with the upgrading. Reading releasenotes often end up in checking out the new features and what to do with them, what they are for and how you can use them, while upgrading first should focus on keeping the existing functionality working as it should (or improve it). And only after that, start with the cool new stuff.

If my answer helped you in any way, please then mark it as helpful. If it resolved the issue, please mark it as correct. This way others will find it in the solved queue and helps them on similar queries.

Mark