updated README and release notes
MODIFY
README.rdoc
README.rdoc
@@ -121,8 +121,7 @@ distribution.
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Hack along and test your code using rake test and rake
- cucumber. You must start consul in order to use cucumber.
+3. Hack along and test your code.
4. Commit your changes (`git commit -am 'Add some feature'`)
5. Push to the branch (`git push origin my-new-feature`)
6. Create new Pull Request
@@ -130,6 +129,37 @@ distribution.
Don't increase the gem version in your pull requests. It will be done after merging the request,
to allow merging of pull requests in a flexible order.
+== Running the tests
+
+Beetle ships with a cucumber feature to test the automatic redis failover
+as an integration test.
+
+To run it, you have to start a RabbitMQ server and a consul
+development mode.
+
+The top level Rakefile comes with targets to start several RabbitMQ
+instances locally. Make sure the corresponding binaries are in your
+search path. Open two shell windows and execute the following command:
+
+ rake rabbit:start1
+
+and
+
+ rake consul:start
+
+Then you can run the cucumber feature by running:
+
+ cucumber
+
+or
+
+ rake cucumber
+
+
+Note: Cucumber will automatically run after the unit test when you run rake.
+
+
+
== How to release a new gem version
Update RELEASE_NOTES.rdoc!

MODIFY
RELEASE_NOTES.rdoc
RELEASE_NOTES.rdoc
expiry times.
* added delete_queue_keys command to beetle to allow deletion of
excess dedup store entries for a given queue.
+* config server: store current master server in consul, if consul
+ config has been provided.
+* config server: server correctly updates configured client ids when
+ they change in consul.
== Version 3.0.0.rc1
* provide client method to setup queues and queue policies.

DELETE
features/README.rdoc
-=== Cucumber
-
-Beetle ships with a cucumber feature to test the automatic redis failover
-as an integration test.
-
-To run it, you have to start a RabbitMQ.
-
-The top level Rakefile comes with targets to start several RabbitMQ instances locally.
-Make sure the corresponding binaries are in your search path. Open a new shell
-and execute the following command:
-
- rake rabbit:start1
-
-Then you can run the cucumber feature by running:
-
- cucumber
-
-or
-
- rake cucumber
-
-
-Note: Cucumber will automatically run after the unit test when you run rake.

updated README and release notes