# Upgrade Button - Possible Window to Exploits

**URL:** <https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877>\
**Category:** Feature\
**Created:** [10 Setembro , 2014 16:14 UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877 "2014-09-10T16:14:17Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [10 Setembro , 2014 22:41 UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877/5 "2014-09-10T22:41:49Z")

</div>

> [@Omni](#):
>
> there should be an option to install the latest stable and latest unstable version.

This is complicated from the web UI for a couple of reasons

1. You can not move back to “stable” after being on “tests-passed” until the next major release
2. The web runs in the container, it would have to reach out of the container to make that change

What we can do is link to all this information from the web UI so people are not surprised.

---

_[View the full topic](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877)._