Publish release nodes with tag message from corresponding Git tag

Following the current instructions, which are different for creating tags/releases, there is no input for such message, although it could be a nice idea.

This seems like a neat idea to me and perfect for consideration in phase 3, since the team can't respond to this in our last 14 days before launch.

Tagging Git Phase 3 so it will be on our plate to consider and prioritize, and marking postponed for now.

Thanks for the feedback!

marked as duplicate: #1023638: Use tag annotation for the default release node body.

Since it's come up in conversation a couple of times recently:

The audience of release node text is specifically intended to be non-developers. Release node text is supposed to make recommendations whether it's appropriate to even be testing the release if you're not actively developing, etc. so copying a commit message into it actually works against its purpose.

That would be useful. I have a basic idea how to implement this - I'll try to reach out for sdboyer to discuss this with him to get it going.

Ok. These are the steps:

• #1322648: Add a default VersioncontrolTag::getMessage(), that backends can override to provide tag annotations
• #1322656: Let the Git backend implement VersioncontrolTag::getMessage()
• Add support for this in the project module.

I would go even further: just create the release nodes with the tag message, *if present*. That would make releases so much easier, especially for multi-module distributions like openatrium.

In fact, i would even go as far as saying this is not really useful *unless* the release nodes are automatically created.

Since they would be created only if the tags were annoted, this wouldn't disrupt the current workflow... Plus releases would be created only if tags respected the naming convention so arbitrary non-release (but annoted) tags could still be pushed.

Anyone working on this these days?

I've not been doing anything here for a while. Unassigning for now.

For those wanting something in between, http://drupal.org/project/grn is an option.

-1 on creating the release node itself automatically from annotated tags. For one thing, there'd be no way to properly configure the Release type taxonomy terms for the release node in that case (e.g. for security releases).

But I wouldn't mind pre-populated the release notes field from an annotated tag if it exists. I haven't looked closely at all that code to know exactly where such logic would live, probably in versioncontrol_project_git from versioncontrol_project since annotated tags are presumably completely specific to Git...

p.s. I hate comment_alter_taxonomy and D6 issue tags. :/ WTF was that about? I didn't touch the tags at all... please re-tag if those are relevant to something. Sorry.

Yes. Pre-populating the node body was exactly the idea, if I remember correctly.

Correct. I was replying to the change in scope proposed at #9.

I would prefer to create those release nodes automatically. We can always go back and edit them to change the taxonomy type.

+1 for for automatic release node creation. Prepopulating isn't saving much effort, when half of that is just a copy paste from 'drush rn'. A bunch of clicking around in d.o could be avoided though, and just done directly in git. That would be lovely!

Make an initila issue summary with a proposal