I have noticed lots of people recently assume that creating a new development branch (6.x-1.x) or a new tag (6.x-1.0) automatically creates the release on Drupal.org, which is not the case. I think the Git instruction tab needs to link to the Creating a project release below the 'Creating Releases' section.

Files: 

Comments

+1 - I just fell foul of this (which made me feel quite dumb, as it's nothing new, but I think it used to be part of the old CVS release process docs and, with there being no reference to it in the new docs, I completely forgot!)

Assigned:Unassigned» eliza411
Status:Active» Fixed

Makes sense to me. Done.

Project:Git on Drupal.org» Project Git instructions
Version:» 6.x-1.x-dev
Status:Fixed» Needs review
StatusFileSize
new1.03 KB

This change was made in the config. Committing to the defaults with this patch:

Status:Needs review» Reviewed & tested by the community

Works perfectly for me.

Looks good.

About the changelog file, adding a new header for every change seems somewhat over the top. It's easier to just group it all together and start a new header after a release.

Status:Reviewed & tested by the community» Fixed

committed.

@helmo: Sorry about that. I was trying to follow sdboyer's advice to link to the CHANGELOG to make it easy for people to find when we made significant changes to the commands we are recommending, but GitWeb makes that a nightmare, and the format doesn't work for you, so I've added a docs page instead: http://drupal.org/node/1134632

That's better anyway, since what we need to show is when the change was made on d.o. which is entirely independent of the commit process.

I have another change to commit, so I'll fix it up in that one.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.