Am Mittwoch, 28. Februar 2018 11:01:04 UTC+1 schrieb Edward K. Ream: > > On Wed, Feb 28, 2018 at 3:39 AM, 'Marcel Franke' via leo-editor < > [email protected] <javascript:>> wrote: > >> >> The usual way to do this today: >> >> master as stable. >> develop as unstable. >> release as pre-stable. >> >> Some visualization of it: >> https://blog.seibert-media.net/wp-content/uploads/2014/03/Gitflow-Workflow-3.png >> > > It's a nice visualization. It's easy to see why it's a popular model. > > However, Leo's master branch is stable enough for daily use, despite being > the target of all development. The point, imo, of pulling master is too get > bleeding edge stuff. > > The purpose is seperation of responsability, decoupling of processes and enforcing more repitation to get better control of code.
It doesn't matter how stable or unstable develop-branch becomes, but master has to be stable and reliable all the time, always. It's the version you sell to the customer, the front that delivers the product. If you fuck up something in develop, it doesn;t matter for the customer, because they use stable. If someone brings in harmful code, it's doesn't matter, because nobody is supposed to have access to master except the maintainer, and he reviews and knows everything that goes in master and should see the harmful code. Additionally because everything should be already reviewed when being merged to develop, with the review of the release-code you make a second review. But this time it's a release-wide review, a more global view you could say, compared to the more local review of a featuer-merge. The reviewer is able to see how the differnt seperate features fit together, and simply makes a second run on the code. It doesn't matter how stable you think your code is, or how good of a coder you are, testing things multiple times always enhances quality because you iterate the code now with the knowledge you gained from previous reviews and all development that happend in the meanwhile. And of course, as a human you always miss something because nobody is perfect all the time. For any mildly complex project a proper wokflow is neccessary to not drift into low quality and building technical debt. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
