# Plugin post-voting conflicts with previous question-answer-plugin

**URL:** <https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372>\
**Category:** Self-hosting\
**Tags:** post-voting\
**Created:** [December 9, 2022, 11:35am UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372 "2022-12-09T11:35:59Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![gmoirod](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gmoirod/32/263768_2.png) [@gmoirod](https://meta.discourse.org/u/gmoirod)\
**Post date:** [December 12, 2022, 1:13pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/21 "2022-12-12T13:13:20Z")

</div>

> [@JammyDodger](#):
>
> I’m afraid my knowledge about the Stable branch is fairly limited, but I think it’s geared more towards not changing things very often. So I would think adding new plugins and extras outside of a Stable release window would be counter-intuitive to that?

Touché 😬  
Keeping “stable” Discourse and following latest plugins changes does not make sense…  
BUT ! Upgrading Discourse (to get security fixes for example) automatically upgrades plugins. Then again, no way to pin them…  
So how to get Discourse patch updates without upgrading plugins ?

> [@JammyDodger](#):
>
> Managed hosting also makes this process easier too as an alternative, as they’ll handle all of the technical stuff and let you concentrate on your community.

1 point for SaaS offer ! 🙂

---

_[View the full topic](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372)._
