If the tag for a release is annotated, should we use the annotation as the default body for a release node using that tag? It could make the process of creating a release faster. On the other hand, you can't use cvs/git-release-notes.php until after the tag is created, so you couldn't add the changelog to the tag. Also, document the git tag -a if we do this.

Comments

Josh The Geek’s picture

Josh The Geek commented

Actually, you can use git-release-notes.php (http://github.com/JoshTheGeek/git-release-notes) like this: ~/git-release-notes.php 6.x-1.0 6.x-1.x.

lut4rp’s picture

lut4rp commented

I'm +1 on the "use annotated tags" thought for both the reasons -- we get release notes from tags automatically (if done?) and proper contributor information is stored (both, tagger and last committer).

(For reference, I had posted a detailed reasoning here: #1073690: Use real tags instead of lightweight ones)

marvil07’s picture

marvil07 commented

If the annotated tag message is a simple text added by the maintainer, it makes sense.

But I do not see the output of http://drupal.org/project/grn (there is the new home) inside the annotated tags itself(IMHO we do not want html on the tag message), but we do want that output in the release node.

Josh The Geek’s picture

Josh The Geek commented
Status: Active » Closed (won't fix)

marvil07: It was just a suggestion, but I agree that I shouldn't route grn's html into git tag -a.

Josh The Geek’s picture

Josh The Geek commented
Status: Closed (won't fix) » Closed (duplicate)

of #1050618: Publish release nodes with tag message from corresponding Git tag