# QA checklist for when new versions are released?

**URL:** <https://meta.discourse.org/t/qa-checklist-for-when-new-versions-are-released/81678>\
**Category:** Product Support\
**Created:** [February 27, 2018, 4:31pm UTC](https://meta.discourse.org/t/qa-checklist-for-when-new-versions-are-released/81678 "2018-02-27T16:31:24Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)\
**Post date:** [March 2, 2018, 12:07am UTC](https://meta.discourse.org/t/qa-checklist-for-when-new-versions-are-released/81678/11 "2018-03-02T00:07:34Z")

</div>

That’s a good point to make. I should probably elaborate why SP has its own testing document then. We have it because we’re one of the very few instances that runs off a fork, so merge issues can occur and we don’t necessarily run all the tests to ensure functionality still passes after the merge is done.

So let that be warning to not use a fork, it adds complexity and requires additional resources to ensure everything is functioning as it should.

---

_[View the full topic](https://meta.discourse.org/t/qa-checklist-for-when-new-versions-are-released/81678)._