I am attempting to make a development release of the FBOauth project.

I have created a 7.x-1.x branch of this project and committed it.
https://www.drupal.org/node/1131300/commits

I click on the "Add New Release" link at the bottom of the FBOauth project page, which is the link:

https://www.drupal.org/node/add/project-release/1131300

and I get the error message:


No valid branches or tags found.
Your release needs to have a tag or branch that follows the naming conventions and have no other release attached to it.

Valid release tag examples:

7.x-1.2
7.x-2.0-alpha2
7.x-2.0-beta3
Valid release branch examples:

7.x-1.x
6.x-2.x
For more help, see Creating a Tag or Branch in Git or the Git instructions page for your project.

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

Is something broken on the Drupal.org website or am I doing something wrong?

Comments

dman’s picture

dman commented

The 7.x-1.x branch already exists - as seen on http://cgit.drupalcode.org/fboauth
and there is a release node for that at https://www.drupal.org/node/1131300/release
And all the tags there have got release nodes already also
... the message that says there are "no valid branches or tags" is telling you there are no branches or tags that don't already have release nodes attached

I don't know what you were trying to do when you "created" a 7.x-1.x branch that already existed since 2011, but that seems to be where the confusion is.

If you really want to create a new branch, it should be named something new : 7.x-2.x
If you were trying to add a new stable release for download, it should TAGGED, 7.x-1.7 not a new branch
If you just wanted the tarball for 7.x-1.x to be re-rolled, just wait for a bit and the system will rebuild for you over time. Usually that becomes available within an hour for public projects. fboauth 7.x-1.x-dev looks like it's reasonably fresh.
If you want the dev release to show up on the project page, it looks like you should Check your settings at Administer Releases

darrellduane’s picture

darrellduane commented

The issue was with the Administer Releases settings. I didn't know what a "Snapshot" release was. I now see that it is a Development Release.

I have checked this box and now it appears.

What would it take to rename "Snapshot" to be "Development" on this page? Wouldn't that make more sense?

Thanks for your help, dman.

dman’s picture

dman commented
Status: Active » Fixed

Terminology is a funny old thing. I would agree that "Development snapshot" would be a accurate label for there though.

darrellduane’s picture

darrellduane commented

Great, I've created a new issue asking for two fixes to be added to Drupal.org so that this confusion is eliminated. https://www.drupal.org/node/2385781

Status: Fixed » Closed (fixed)

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