Link to instructions on the new release page

Thanks for bringing this up again. It needs to happen, but I'm not really sure a developer issue was ever opened, nor can I assure you it will in as timely a fashion as we might like, but it's important. Assigning to me until I'm sure it's represented in the developer queue.

There was never an issue that I know of. If someone posts a link to the right documentation to link here, I'll add the link via a form_alter in drupalorg_project.

I would link here: http://drupal.org/node/1015226 and make sure it cross-references the specific commands page (which it's not currently doing). There's still a lot of flux in the docs.

Another enhancement I'd like to see at the first opportunity after deployment, postponing and tagging for now.

+1
More than just a link to instructions, I'd encourage you to show a example tag/branch names:

Text such as:

Tags should be in the form of Drupal Dist-Project Release. Valid examples include:
7.x-1.0
7.x-1.0-beta5
7.x-2.0-alpha3

Branch Names should be in the form of Drupal Distribution-Project Distribution. An example is:
7.x-2.x (no need to include -dev, it will be appended automatically if the tag or branch name ends in .x)

For more details visit this page.

For a quick guide to adding tags and branches for Git on Drupal, visit this page.

This has pretty serious implications for the UX and support load we're going to get, so I'm bumping to major. Here's 2 patches (one to remove a // TODO from versioncontrol_release to make this text easily alterable, and then the altering itself in drupalorg_versioncontrol), plus before/after screenshots of how it looks in bluecheese. Mostly incorporated DarrellDuane's approach from #5 but with some edits.

Wearing my UX hat, this is way too much text. Here's another version that clobbers the default text from versioncontrol_release (instead of appending to the end of it) and makes it all more concise. Also includes a link to the Git instructions tab. Same before and vc_release patch from #6. New patch for drupalorg_versioncontrol and new after.png.

*MUCH* better. I think that looks great.

No valid branches or tags found.

Your release needs to have a tag or branch that follows the naming convention and have no other release attached to it.

Valid release tag examples :

Valid release branch examples:

.....

Once you have added a valid branch or tag, try again.

This implements Bojhan's suggestions (but leaving the actually error message itself bold), which I confirmed in IRC Bojhan is still happy with.

This looks great to me, too.

:)

Great! Committed #6 to HEAD of versioncontrol_project and #10 to DRUPAL-6--3 of drupalorg. Yay!

This is no longer a leftover. ;)