I guess that pointing to a dedicated git-sha is not a very good option. What do you think?
You mean pointing to a git revision within the published version of PropCheck? I don't know if this is something that is frowned upon.. How about this: We point to PropEr's git revision, but only release a RC candidate. With that, the update of PropCheck should not automatically propagate to users, unless they explicitly switch to the RC version.
maybe_improper_list()and so on either.
alfert/propcheck#200 Would you like that to be merged, or should we close and simply update to the new PropEr release when it is released?
I guess we don't need to merge, we simply wait for the release, upgrade then the dependencies and release PropCheck 1.4