abstract_feature_branch

abstract_feature_branch

abstract_feature_branch is a Rails gem that enables developers to easily branch by abstraction as per this pattern: http://paulhammant.com/blog/branch_by_abstraction.html It is a productivity and fault tolerance enhancing team practice that has been utilized by professional software development teams at large corporations, such as Sears and Groupon. It provides the ability to wrap blocks of code with an abstract feature branch name, and then specify in a configuration file which features to be switched on or off. The goal is to build out upcoming features in the same source code repository branch, regardless of whether all are completed by the next release date or not, thus increasing team productivity by preventing integration delays. Developers then disable in-progress features until they are ready to be switched on in production, yet enable them locally and in staging environments for in-progress testing. 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. abstract_feature_branch additionally supports DDD's pattern of Bounded Contexts by allowing developers to configure context-specific feature files if needed.

Rubygem abstract_feature_branch

Total Downloads
34143
Releases
26
Current Version
1.2.2
Released
2014-02-23 00:00:00 UTC
First Release
2012-11-12 00:00:00 UTC
Depends on following gems
Depending Gems
0

Github AndyObtiva/abstract_feature_branch

Watchers
5
Forks
2
Development activity
Active
Last commit
2014-01-27 01:34:29 UTC
First commit
Top contributors
Contributors
4
Issues

Resources

There are no resources yet, be the first to submit one!

Comments

There are no comments yet, be the first to write one!

Post a comment

Markdown supported
or
×

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.