The discussion revolves around whether Discourse plugins have stable versions, with EricGT raising the issue that plugin upgrades often cause problems for admins. Stephen directs users to a meta topic on pinning plugin and theme versions for older Discourse installs. RGJ highlights the new plugin version pinning feature as the future solution and mentions that their third-party GitHub account maintains forks of plugins compatible with the latest stable release, often tagged for older versions. featheredtoast expresses hope that the pinning system will reduce maintenance burdens, noting that Communiteq (formerly DiscourseHosting) follows stable releases by default, unlike CDCK hosting which follows tests-passed. They invite contributions via PRs for .discourse-compatibility files to help stabilize popular/core plugins. RGJ confirms they will begin adding those files immediately whenever a plugin breaks on stable. The community is actively working toward better version control and stability for plugins, especially for admins who prefer not to risk upgrading to untested versions.
In reading many post for the past few months one of the main reasons Discourse admins run into problems is that certain plugin upgrades cause problems.
If certain plugin versions are marked as stable then for those not needing the latest and greatest versions, we can wait for a stable version instead of clicking the upgrade button and crossing our fingers.
The new plugin version pinning feature is the way forward.
In the meanwhile, for plugins that do not support that (yet), we - as an independent third party - maintain a Github account with plugin forks on commits that are compatible with latest stable. Most plugins there are also tagged for older versions.
I’m hoping that the new pinning system will lessen the maintenance pain on all sides!
Communiteq (formerly DiscourseHosting) probably notices it a lot more since you guys follow stable by default too, whereas CDCK hosting follows tests-passed. Feel free to PR .discourse-compatibility files so we can get the ball rolling a bit at least for the popular/core plugins!