# Issues to address to get out of beta

**URL:** <https://forum.duplicati.com/t/issues-to-address-to-get-out-of-beta/7871>\
**Category:** Developer\
**Created:** [August 25, 2019, 1:03am UTC](https://forum.duplicati.com/t/issues-to-address-to-get-out-of-beta/7871 "2019-08-25T01:03:50Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![kenkendk](https://forum.duplicati.com/user_avatar/forum.duplicati.com/kenkendk/32/5305_2.png) [@kenkendk](https://forum.duplicati.com/u/kenkendk)\
**Post date:** [August 30, 2019, 8:27am UTC](https://forum.duplicati.com/t/issues-to-address-to-get-out-of-beta/7871/25 "2019-08-30T08:27:20Z")

</div>

> [@warwickmm](#):
>
> Back on the topic of release workflow…I strongly agree with the need for regular (possibly automated) canary releases. Without these, we will often have the issue (like now) where changes sit basically untested by users.

I know @verhoek set up an automated system for producing nightly builds that were signed with a different key (on the build server). I completely dropped that one, but I am sure it can be picked up if there is a push for it.

> [@BlueBlock](#):
>
> no backup data corruption, including application crashes during backup (though in-progress backup might be invalid/lost?)

This is what I consider the blocker for a non-beta release. The database rebuild is super slow, and sometimes fails. For a production-ready system this should not happen.

There are also cases where the database suddenly breaks, but maybe that part is actually fixed now.

The shutdown is nice, but Duplicati _should_ be able to handle a hard power off, so that is not a blocker for me. Symlinks and paths are working AFAIK, and some translations are complete.  
Subfolders is a new feature, so I would not delay a non-beta for that.

---

_[View the full topic](https://forum.duplicati.com/t/issues-to-address-to-get-out-of-beta/7871)._
