Best Practice for Updating Plugins

[SM_Toronto]

Gurus and Experts,

What is the best practice for updating plugins that are already existing/installed in our system?

Do they update by themselves? Or what is the best discipline?

TIA,

SM

[Jaspal Singh · Accepted solution]

Hi,

Plugins do not auto-upgrade itself. It happens only for cases when the platform version itself is upgraded from one release to another.

Well, before upgrading you can go through the release docs to understand the impact & benefits your application might have if upgraded. Again, platform upgrade is a major activity & plugin upgrades are also taken care holistically.

In case, you wish to update plugins regardless of platform upgrade, you need to do it manually.

[SM_Toronto]

Our Best Practice now is to update existing plugins during Version Upgrade process. Here are our high-level steps:

1) Clone over DEV (from PROD)

2) Upgrade the next Family Version (e.g. Utah Patch 4b to Vancouver Patch 1)

3) Navigate to the Plugins module and select "updates" and update each available plugins and list them down (as part of the deployment package).

[ctsmith]

Thanks Jaspal.  A follow-up here... Are you saying a major version upgrade package will update all plugin applications to A version that is compatible with the upgrade?  But maybe it's not the most recent update to the plugin since the major upgrade version only contained the updates to the plugins at that time?  So like we upgrade to Xanadu 4 and that comes with HAM application v 1.1 for Xanadu but there's actually a 1.2 for Xanadu.  Does that make sense?

[ctsmith]

I think the additional catch here is that the current plugin version you're on doesn't tell you which version it's for.  It only tells you which version the updates are for.  The installed version doesn't reference any major versions (X,Y,Z):