Add revision IDs to releases #14
Description
A not so critical issue but something that would be very helpful. But it would be great if the revision hash for each version was added to release assets as a file OR better, if it can be added to the release message as a set of individual code blocks. That way, developers can easily copy and paste the revision number into their requires statements to ensure they get the exact revision they wanted.
I thought about removing the version and just having revisions OR making the versions based on the recipe and not the binaries. We could do this, but the conan settings.yml file only has the major number for clang so we couldn't do patches and minor versions. We could even add an additional conan option to specify a specific version and provide defaults if the compiler.version is the only information available. But, I'm not sure how much better that is. It feels like another option, but I think the only real con to this is that we will have more overall versions to contend with and more memory may be wasted holding identical copies of the same recipe. But I'm okay with that. For now. Until it starts to matter. I hope that this project won't need too many revisions making a need to optimize this irrelevant.