Hi, Currently, Hydrogen development takes place in one master branch ans several feature branches. That model is simple, but is not optimal because upcoming releases "clog” master branch and pull requests are kept in limbo state, gradually becoming out of sync with master. In order to fix this, I propose to split master branch into three branches: „development”, „testing” and „release” branches.
Features would be developed in feature branches, just like now. When completed, feature branches would be merged into „development” branch. This would allow to shorten feedback loop for developers, who get chance to see earlier how their features integrate with other peoples’ features, and advanced users could check this branch to see what’s going on in Hydrogen development. Once enough features have been accumulated in „development” branch, it is merged into „testing” branch. Release candidates (beta versions) are created from this branch. Any bugs would be fixed in branches created from „testing” and merged back into „testing” and then backported to „devel”. When code in „testing” branch matures, it is merged into „release” branch. Regular releases would be made from this branch. Bugs found in released versions would be fixed in branched started from „release” branch and merged back there, then backported to „testing” and „development”. That model adds some bookkeeping comared to current model, but is more flexible at the same time - it allows to work on new features, prepare releases and fix bugs at the same time. I have succesfully used this model at my previous employer and very similar model at my current employer and find it very powerful. Please let me know what do you think about it. Regards, Przemek ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Hydrogen-devel mailing list Hydrogen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
