On Sep 18, 2009, at 3:40 PM, Josh Thompson wrote:

(2) pros - not as easy as #1, but still pretty easy
        - if a vote fails, just create another tag
   cons - same cons as #1, plus:
- could result in many tags that could make subversion a little

A tag is best, IMO.

If a vote fails, then you can always delete the corresponding directory in tags/ (this reduces the apparent clutter). And then spin a new release candidate for a new vote. Then a question of whether or not your tags have unique names (e.g. 0.5-RC1, 0.5-RC2, etc or just 0.5 w/ corresponding revision #). I've seen communities use either approach. Personally, I prefer simple name (e.g. 0.5 and note the revision number in the release).

My current understanding is that: technically, a release vote is not on the code that is in SVN. Instead the vote is on the source archive that the release manager has created (which has been digitally signed). Expectation is that the source archive matches the tag code (and this should be verified during release vote).


Reply via email to