On a new Drupal.org project it seems logical to enable dev snapshots even before tagging any alpha release.

I pushed a branch and created a dev release node for it: https://drupal.org/node/2262939

But I still got "No release versions for this project exist." on /node/2217793/edit/releases

And thus could not enable the "Show snapshot release" checkbox. Only after tagging a useless 7.x-3.0-alpha1 version could I enable showing the snapshot release on the project node.

I've traced this to project_release_project_edit_form() in release/includes/project_edit_releases.inc.

Would it be possible to make the query there aware of dev release nodes?

Comments

drumm’s picture

I was able to show 7.x-3.x-dev for https://drupal.org/project/drupalorg, which doesn't have any tagged releases. (I hid it again, because it isn't really useful to download that tarball.)

I think the problem is that project_release_supported_versions hadn't been updated properly. Without seeing this as it happens, it would be hard to say if this is a problem with project release module, or just happening on Drupal.org. That table would have been updated when the new release was packaged, putting everyhting into the correct place.

Maybe the admin releases page could be more defensive and call project_release_check_supported_versions() if it seems needed, or regardless.

helmo’s picture

Raphael Apard’s picture

Status: Active » Needs review

Go to "View all releases", click on your development release.
Click on the "Edit Tab", check "Show in project’s download table when branch is supported" and save.

drumm’s picture

Category: Bug report » Support request
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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