When can this package go to at least 1.x?
Issue #14
new
Seems it has been burnt in enough that would justify a major version number > 0.
Seems it has been burnt in enough that would justify a major version number > 0.
If this is claimed to be production ready than IMO it should be at least 1.0