/hg/release/icedtea6-1.5: Added tag icedtea6-1.5.3 for changeset...

[Andrew Haley]

Mark Wielaard wrote:

> On Wed, 2009-09-02 at 13:45 +0100, Andrew John Hughes wrote:
>> That's my opinion as well.  We now seem to have two tags (1.5.2 and
>> 1.5.3) for non-existent releases.  The last release is still 1.5.1 and
>> that's the only one of these I can download a tarball for from
>> http://icedtea.classpath.org/download/source/.  I agree the tags
>> shouldn't move, but that only applies after a release has being made.
>> I doubt anyone is going to be relying on this 1.5.2 tag as the only
>> evidence of it is a single commit e-mail.  I also think it should be
>> fairly obvious that adding a tag does not constitute a release, but it
>> seems that isn't the case.
> 
> OK, apparently I am the only person who assumes tagging something with
> an official release name shows intent to do a release from that commit.
> IMHO it would be better to only tag official releases with official
> (sounding) release names. But in any case, please do communicate about
> the intent of any commit you make to avoid any confusion.

Yes.  It is probably best to name the tag icedtea-1.5.x-candidate-N and then
only make the icedtea-1.5.x-release tag when the release actually happens.
That way, you don't have to explain what the tag means: it's in the name.

Andrew.