On Jan 12, 2012, at 5:36 AM, Sylvain Lebresne <sylv...@datastax.com> wrote:
> Note that I had to adapt a little bit to the switch to git. In particular,
> instead of using sha1 to mark the tentative commit of a release, I've decided
> to use a lightweight tag, namely 1.0.7-tentative. My goal being that once the
> vote passes, I'll delete this temporary tag and create the actual
> cassandra-1.0.7 tag. My rational for not creating the final tag right away is
> that:
> - I want it to be clear 1.0.7 is not yet released
> - If the vote fails, we would have to delete the tag anyway
> If someone has a problem with that, let me know.
I'm -1 on not announcing a specific commit hash, for historical purposes. Tags
can be changed (and probably will be under this approach, if we have to
reroll), or deleted, and they may not even agree between different repos. With
a sha1, there is no ambiguity about which exact snapshot is being (or was)
voted on.
It's still probably a good idea to have a tag, as you say
("prospective/1.0.7/1" maybe? I find tag namespaces come in handy), but it
should be intended for convenience only.
p
