Rubygems | Latest Versions for abstract_feature_branchhttps://rubygems.org/gems2024-01-22T20:44:52Zabstract_feature_branch (1.6.0)https://rubygems.org/gems/abstract_feature_branch/versions/1.6.02024-01-22T20:44:52ZAndy Malehabstract_feature_branch is a Ruby gem that provides a variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler (aka Feature Flags) to enable Continuous Integration and Trunk-Based Development.
abstract_feature_branch is a Ruby gem that provides a unique variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler to enhance team productivity and improve software fault tolerance.
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 (i.e. Continuous Integration and Trunk-Based Development), 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 Domain Driven Design's pattern of Bounded Contexts by allowing developers to configure context-specific feature files if needed.
abstract_feature_branch is one of the simplest and most minimalistic "Feature Flags" Ruby gems out there as it enables you to get started very quickly by simply leveraging YAML files without having to set up a data store if you do not need it (albeit, you also have the option to use Redis as a very fast in-memory data store).
abstract_feature_branch (1.5.1)https://rubygems.org/gems/abstract_feature_branch/versions/1.5.12023-02-14T14:45:42ZAndy Malehabstract_feature_branch is a Ruby gem that provides a variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler (aka Feature Flags) to enable Continuous Integration and Trunk-Based Development.
abstract_feature_branch is a Ruby gem that provides a unique variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler to enhance team productivity and improve software fault tolerance.
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 (i.e. Continuous Integration and Trunk-Based Development), 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 Domain Driven Design's pattern of Bounded Contexts by allowing developers to configure context-specific feature files if needed.
abstract_feature_branch is one of the simplest and most minimalistic "Feature Flags" Ruby gems out there as it enables you to get started very quickly by simply leveraging YAML files without having to set up a data store if you do not need it (albeit, you also have the option to use Redis as a very fast in-memory data store).
abstract_feature_branch (1.5.0)https://rubygems.org/gems/abstract_feature_branch/versions/1.5.02023-02-12T00:36:32ZAndy Malehabstract_feature_branch is a Ruby gem that provides a variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler (aka Feature Flags) to enable Continuous Integration and Trunk-Based Development.
abstract_feature_branch is a Ruby gem that provides a unique variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler to enhance team productivity and improve software fault tolerance.
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 (i.e. Continuous Integration and Trunk-Based Development), 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 Domain Driven Design's pattern of Bounded Contexts by allowing developers to configure context-specific feature files if needed.
abstract_feature_branch is one of the simplest and most minimalistic "Feature Flags" Ruby gems out there as it enables you to get started very quickly by simply leveraging YAML files without having to set up a data store if you do not need it (albeit, you also have the option to use Redis as a very fast in-memory data store).
abstract_feature_branch (1.4.0)https://rubygems.org/gems/abstract_feature_branch/versions/1.4.02023-02-05T22:05:50ZAndy Malehabstract_feature_branch is a Ruby gem that provides a variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler (aka Feature Flags) to enable Continuous Integration and Trunk-Based Development.
abstract_feature_branch is a Ruby gem that provides a unique variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler to enhance team productivity and improve software fault tolerance.
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 (i.e. Continuous Integration and Trunk-Based Development), 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 Domain Driven Design's pattern of Bounded Contexts by allowing developers to configure context-specific feature files if needed.
abstract_feature_branch is one of the simplest and most minimalistic "Feature Flags" Ruby gems out there as it enables you to get started very quickly by simply leveraging YAML files without having to set up a data store if you do not need it (albeit, you also have the option to use Redis as a very fast in-memory data store).
abstract_feature_branch (1.3.3)https://rubygems.org/gems/abstract_feature_branch/versions/1.3.32023-01-15T17:17:30ZAndy Malehabstract_feature_branch is a Ruby gem that provides a variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler (aka Feature Flags).
abstract_feature_branch is a Ruby gem that provides a variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler.
It is a productivity and fault tolerance enhancing team practice.
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 (i.e. continuous integration), 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 Domain Driven Design's pattern of Bounded Contexts by allowing developers to configure context-specific feature files if needed.
abstract_feature_branch is one of the simplest and most minimalistic "Feature Flags" Ruby gems out there as it enables you to get started very quickly by simply leveraging YAML files without having to set up a data store if you do not need it (albeit, you also have the option to use Redis as a very fast in-memory data store).
abstract_feature_branch (1.3.2)https://rubygems.org/gems/abstract_feature_branch/versions/1.3.22022-12-12T14:51:38ZAnnas "Andy" Malehabstract_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
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.
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.
abstract_feature_branch (1.3.1)https://rubygems.org/gems/abstract_feature_branch/versions/1.3.12022-12-12T00:50:23ZAnnas "Andy" Malehabstract_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
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.
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.
abstract_feature_branch (1.3.0)https://rubygems.org/gems/abstract_feature_branch/versions/1.3.02022-12-11T23:49:56ZAnnas "Andy" Malehabstract_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
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.
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.
abstract_feature_branch (1.2.2)https://rubygems.org/gems/abstract_feature_branch/versions/1.2.22014-02-23T18:42:34ZAnnas "Andy" Malehabstract_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
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.
abstract_feature_branch (1.2.1)https://rubygems.org/gems/abstract_feature_branch/versions/1.2.12014-01-23T17:17:32ZAnnas "Andy" Malehabstract_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
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.
abstract_feature_branch (1.2.0)https://rubygems.org/gems/abstract_feature_branch/versions/1.2.02014-01-19T22:48:29ZAnnas "Andy" Malehabstract_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
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.
abstract_feature_branch (1.1.1)https://rubygems.org/gems/abstract_feature_branch/versions/1.1.12014-01-14T16:34:43ZAnnas "Andy" Malehabstract_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
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.
abstract_feature_branch (1.1.0)https://rubygems.org/gems/abstract_feature_branch/versions/1.1.02014-01-14T16:28:44ZAnnas "Andy" Malehabstract_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
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.
abstract_feature_branch (1.0.0)https://rubygems.org/gems/abstract_feature_branch/versions/1.0.02013-11-26T22:25:45ZAnnas "Andy" Malehabstract_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
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.
abstract_feature_branch (0.9.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.9.02013-11-26T21:22:04ZAnnas "Andy" Malehabstract_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
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.
abstract_feature_branch (0.8.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.8.02013-11-25T22:05:43ZAnnas "Andy" Malehabstract_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
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.
abstract_feature_branch (0.7.1)https://rubygems.org/gems/abstract_feature_branch/versions/0.7.12013-11-25T01:22:07ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.7.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.7.02013-11-25T00:45:45ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.6.4)https://rubygems.org/gems/abstract_feature_branch/versions/0.6.42013-11-23T20:36:12ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.6.3)https://rubygems.org/gems/abstract_feature_branch/versions/0.6.32013-11-23T18:54:51ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.6.2)https://rubygems.org/gems/abstract_feature_branch/versions/0.6.22013-11-23T18:07:08ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.6.1)https://rubygems.org/gems/abstract_feature_branch/versions/0.6.12013-11-23T18:03:24ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.6.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.6.02013-11-23T17:58:57ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.5.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.5.02013-11-22T19:08:18ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.4.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.4.02013-11-21T22:54:54ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.3.6)https://rubygems.org/gems/abstract_feature_branch/versions/0.3.62013-11-19T23:03:36ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.3.5)https://rubygems.org/gems/abstract_feature_branch/versions/0.3.52013-11-19T17:02:36ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.3.4)https://rubygems.org/gems/abstract_feature_branch/versions/0.3.42013-11-19T16:30:07ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.3.3)https://rubygems.org/gems/abstract_feature_branch/versions/0.3.32012-12-13T04:43:00ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.3.2)https://rubygems.org/gems/abstract_feature_branch/versions/0.3.22012-12-13T04:41:11ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.3.1)https://rubygems.org/gems/abstract_feature_branch/versions/0.3.12012-12-13T04:24:08ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.3.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.3.02012-12-13T04:18:50ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.2.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.2.02012-11-25T07:02:44ZAnnas "Andy" Malehabstract_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 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.
abstract_feature_branch (0.1.0)https://rubygems.org/gems/abstract_feature_branch/versions/0.1.02012-11-12T13:23:46ZAnnas "Andy" Malehabstract_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 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.