# CALL: Sunday, August 25th at 17:00 UTC

**URL:** <https://discuss.freedombox.org/t/call-sunday-august-25th-at-17-00-utc/340>\
**Category:** Announcements\
**Created:** [August 23, 2019, 2:12pm UTC](https://discuss.freedombox.org/t/call-sunday-august-25th-at-17-00-utc/340 "2019-08-23T14:12:06Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![emorrp1](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/e/48db29/32.png) [@emorrp1](https://discuss.freedombox.org/u/emorrp1)\
**Post date:** [August 25, 2019, 5:21am UTC](https://discuss.freedombox.org/t/call-sunday-august-25th-at-17-00-utc/340/3 "2019-08-25T05:21:33Z")

</div>

Freedombox stable updates. It was a shame 19.2 didn’t make it into buster, but as I understand it, post release restrictions are more like the soft freeze than the full freeze criteria. The descriptive commit breakdown has already been written, but if the release team still object to such a large change all at once, it may be necessary to cherry-pick by severity, including raising BTS bugs to match.

> [@Rename 'testing' to 'Rolling' everywhere](https://discuss.freedombox.org/t/rename-testing-to-rolling-everywhere/67/9):
>
> Most of us understand the appliance mind set and how stable release can cater to it. We put in lot of effort to get ready for stable so that Pioneer Kits could use stable. Some problems though: We wanted to provide not only security fixes but also important fixes for stable users. Unfortunately, backports has a restriction that whatever version is available in testing must go into backports. That didn’t allow us to release 19.2.x with only important fixes to users. We really didn’t want to add…

---

_[View the full topic](https://discuss.freedombox.org/t/call-sunday-august-25th-at-17-00-utc/340)._
