abstract_feature_branch 0.3.6

It gives ability to wrap blocks of code with an abstract feature branch name, and then specify which features to be switched on or off in a configuration file. The goal is to build out future features with full integration into the codebase, thus ensuring no delay in integration in the future, while releasing currently done features at the same time. Developers then disable future features until they are ready to be switched on in production, but do enable them in staging and locally. This gives developers the added benefit of being able to switch a feature off after release should big problems arise for a high risk feature.