jrallison/rollout_ui — pull request #5 by midu (2012-04-10 22:04:47+00:00)
Title: Add ability to create a feature in the UI

## [Bring back ruby 1.8.7 compatibility](https://github.com/midu/rollout_ui/commit/793e82cc1a19b04ddf0f150e15ff098e11576cfa#L1R18)

`Rollout 1.1.0` is not compatible with `ruby 1.8.7` and most of the code in `rollout_ui` does not take advantages of the changes brought by `1.1.0` so I took the liberty allowing the previous version.

(tests pass on both versions)

## [Feature#percentage returns 0](https://github.com/midu/rollout_ui/commit/acf8d7bf309330e649aac8f70b6b2f54c79bd060#L0R13)

Because `nil` and `0`% mean the same thing (here).

## [Remove ActiveRecord from the dummy app](https://github.com/midu/rollout_ui/commit/d8b1b6f93a834fbf5506b0b51c80c2f472ca6471#L0L3)

So no database is needed for testing

## Allow creation of a feature via Rollout UI

This is the main reason for this fork.

We needed a strategy to add a feature in rollout before pushing it from dev to prod (or other environments).

The choices were some rake task to run on deploy or adding the functionality to rollout ui. The latter allows non(-too)-tech people to do it as well and prevents having to ssh onto a server or deploy an app just to create a redis key.

The newly created feature is activated for no one.