dev release isn't appearing on project page

Have the same problem with a different contrib module. https://www.drupal.org/project/commerce_mollie

I also added a recent related issue.

Maybe something changed recently on the Drupal.org side that causes this?

Note that I successfully managed to do this on August 4. That was for a different project. So I am kinda sure the 'Administer releases' behaved different then.

The projects all only have dev releases:

• https://www.drupal.org/project/schema/releases?api_version%5B%5D=7234 (7.x has some tagged releases, which show on the project page.)
• https://www.drupal.org/project/commerce_mollie/releases
• https://www.drupal.org/project/scheduled_executable/releases

With #2688127: Make automated testing results more prominent on project pages, dev releases are now grouped with their tagged release. That issue called for more information about the branch, and grouping the dev and tagged releases for the branch together.

As a side-effect, branches without a tagged release are currently not showing on the project page. If you tag a release, both will show on the project page.

I think this is okay for the average person visiting a project page. Unless you intend to be ready to help with development, or do a decent amount of testing, you probably do not want a dev release. Even if a release is only alpha quality, it is still good to encourage project maintainers to release early and often.

However, this was a side-effect, and would like to hear reasons to show these on project pages.

From my experience, if a project has no releases at all, not even a dev release, then it's not even got any code,

This is also how I see projects without even a dev release.

I'm on the fence about this, It doesn't make much sense when I have modules that now look like they have no code but at the same time I agree with encouraging maintainers to actually tag releases. Certainly helps when using composer.

Maybe we need to promote this change a little more, I had no idea until I created the issue in this queue?

The output of Drupal Association Engineering sprint planning is at https://groups.google.com/a/association.drupal.org/forum/#!forum/changes. This previews our plan for each 2 weeks. Maybe more than most people will be interested in, but it beats following all the issue queues.

We’re currently highlighting deployed changes monthly at https://www.drupal.org/drupalorg/blog. There are some other changes nearby like #2277829: Project status tags are not well documented, so there will be some benefit from being rounded up together.

Show in project’s download table when branch is supported

Maybe this can be set to true all the time and hidden.

Personally I would prefer that a development version is still visible and downloadable even without a tagged release.
Why should it be hidden and only be availably via git?

Personally I would prefer that a development version is still visible and downloadable even without a tagged release.
Why should it be hidden and only be availably via git?

Releases not shown on the project page are downloadable. Click “All releases” toward the bottom of the page.

So either the wording needs to be changed to explain you need a fixed release, or the old behaviour should be restored.

I meant hide the checkbox from the UI, so there is no wording to be incorrect. If there is a dev release to go with a tagged release on the project page, it would always show.

This would also make sure information about the dev branch, like testing results and future additions (such as “N commits ahead of {tagged release}” #2903259: Development version should only appear if different from tagged version) are always shown.

I agree that dev releases should display on the project page. I have a project that only has a dev release, and that's mainly because I want to get some feedback from other users before doing a full release. But they're not going to be likely to try it out if it looks like there is nothing available to download. I think this would be the case with any new project, or any project working on a new major version. I've also found that a lot of dev releases, especially for Drupal 8, work fine.

If the message is that you should create an alpha release then that should be communicated better.

From the feedback here, along with #2903454: How to change the releases shown for download on a project's home page, I’m leaning toward adding back the dev releases section.

For implementing, I only hid that display. The tricky part will be filtering to show only dev branches without a tagged release, so none of them are shown twice.

I was confused by this new behavior as well.

If the message is that you should create an alpha release then that should be communicated better.

+1 to this. I'm fine with the change but it was pretty confusing to me. How about a message that shows to the maintainer that says something like "If you want your dev release to show on the project page then you need to create a tagged release (it can be an alpha or a beta, just has to be a tagged release)."

This affects https://www.drupal.org/project/type_style, I noticed the issue awhile back but didn't circle back to the issue queue.

For implementing, I only hid that display. The tricky part will be filtering to show only dev branches without a tagged release, so none of them are shown twice.

This does sound a little awkward, but I think a layout like:

[8.x-2.0]
>[8.x-2.x-dev]
[8.x-1.0]
>[8.x-1.x-dev]
[8.x-3.x-dev]

[7.x-1.0]
>[7.x-1.x-dev]
[7.x-2.x-dev]

would work - basically keep major version (7/8) releases separate, then sort by default branch releases -> other tagged releases -> dev-without-stable releases. In the above example you wouldn't want 8.x-3.x-dev to be displayed above the tagged releases, and you also wouldn't want it displayed at the bottom of the release list. That's just my opinion, but I think the above example is a good test case.

Another up vote for putting back the link to dev modules.

Dev releases on branches without tagged releases are now back on project pages.

Thank you @drumm!

Cool thanks a lot!

Thank you.

not sure if related but I can't work out why the stock module does not have a dev version visible for the 8 version https://www.drupal.org/project/commerce_stock
Does anyone know if its something I have not set up on the project?

See attached screenshot. I see commerce stock 8.x-1.x-dev on the release page - is that what you mean?

Hi, @greggles I figured it out or more accurately @bojanz did.
I needed to edit the dev version and tick a box "Show in project’s download table when branch is supported ".
If I would have read the thread more carefully would have known that :)