On 27/07/17 17:33, Stefan Schmidt wrote: > Hello. > > On 07/22/2017 11:22 PM, Andrew Williams wrote: >> Hi eflers :) >> >> So after thinking about issue management and planning milestones I >> thought >> more about our source control. We currently have various different models >> used but the bottom line is that it all hits master all the time which >> can >> lead to less stability than ideal and also makes stabilisation windows >> critical to enforce. >> >> As a suggestion I think we should consider agreeing on a singlet >> branching >> model and I'd recommend GitFlow (described quite well here >> https://www.atlassian.com/git/tutorials/comparing-workflows#gitflow-workflow). >> >> As well as being well organised there is a solid gitflow plugin that >> helps >> to manage branches and workflows. > > I read the tutorial now. It is the first time I ever encountered this > workflow. Do you know any bigger FOSS projects that use this? The ones > I'm familiar with do not (not even EDI, which is unstable on master from > time to time. ;)) > Qt uses this workflow or atleast was last time I was paying attention to there development. I'm also in the group thinking this development model is better then our current one (but not enough to passionately argue for it)
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
