# 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:** 20

<div class="post-metadata">

**Author:** ![BlueBlock](https://forum.duplicati.com/user_avatar/forum.duplicati.com/blueblock/32/3309_2.png) [@BlueBlock](https://forum.duplicati.com/u/BlueBlock)\
**Post date:** [August 28, 2019, 7:17pm UTC](https://forum.duplicati.com/t/issues-to-address-to-get-out-of-beta/7871/20 "2019-08-28T19:17:56Z")

</div>

Some info development cycle that I’ve been reviewing. I’m getting used to git in a group as I’ve dealt almost entirely with enterprise environments.

It looks like there are two trains of thought.

One being trunk-based, but I think we can toss this immediately for open source as it does not provide code review and hence low security.

The second is likely what we might want to follow and it is Git Flow.

GitHub has a nice explanation here at time 3:07:  
[https://youtu.be/aJnFGMclhU8?t=187](https://youtu.be/aJnFGMclhU8?t=187)

---

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