Doug Tangren

a common interface for versioned stores

4

starting revisiting a branch I started for a [zookeeper-store](https://github.com/softprops/storehaus/tree/storehaus-zookeeper) and was reminded that there some [versioning semantics](http://zookeeper.apache.org/doc/trunk/zookeeperProgrammers.html#sc_timeInZk) attached to data stored in zookeeper. Mostly as a means of managing and...

consider managing release notes with herald

8

A colleague and myself curate a [tumblr account](http://notes.implicit.ly/) for announcing release notes for scala projects using [herald](https://github.com/n8han/herald#herald) as the primary client. The recipe is simple, you drop a file named...

retrying in storehaus should be a little more configurable

5

The recent addition of retry-able stores was nice but I think the way a client wants to retry should be a little more configurable. Some interfaces where retry apis shine...

MemcacheStore Properties

1

pending some merges from the redis branch for resource cleanup and memcache mergables for new I'd like to put in some unit tests for the memcache module.

This is just a reminder to myself to port this over. I've got a working implementation over [here](https://github.com/softprops/bowhaus/blob/master/src/main/scala/RedisSortedSetStore.scala)

define `map`, `flatMap`, `filter`, and friends for `Delays`

This enables proper tools for error handling which is needed for retrying. See https://docs.aws.amazon.com/systems-manager/latest/APIReference/CommonErrors.html for error docs

## 💡 Feature description Parameter store could potentially by useful for configuration that changes after an application process starts. It's possible to wrap envy-store in something that caches and requires...

Perhaps like conversational git hooks