Although the Leo way is working, it might be advantageous to adopt what has become standard, making potential contributers more comfortable: working on a develop branch instead of master.
Along these lines, issuing pull requests instead of pushing is a good way for changes to be vetted. I was interested to see that Jim Fulton issues pull requests for his changes to his own code base, allowing users to see what he is up to. Certainly hard to know the cost/benefit of any of this stuff. On Wed, Feb 28, 2018 at 4:57 AM, Edward K. Ream <[email protected]> wrote: > On Wed, Feb 28, 2018 at 4:21 AM, 'Marcel Franke' via leo-editor < > [email protected]> wrote: > > It doesn't matter how stable or unstable develop-branch becomes, but >> master has to be stable and reliable all the time, always. >> > > I can understand why organizations might adopt this point of view. > > To my knowledge, having Leo's master be the bleeding edge has never caused > anyone significant problems. > > Edward > > -- > 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. > -- 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.
