Contrib.social

Latest release from maintainer's recommended branch called "Also available", not "Recommended"

Open on Drupal.org →
Created on 11 January 2008, about 17 years ago
Updated 26 April 2024, 9 months ago

Hrm, here's a case I didn't find when pounding on http://drupal.org/node/197186. I'm not even sure this is a bug, but I wanted to submit it for feedback before I worry about a (relatively trivial) patch for it...

Here's the scenario:

- You've got a project with a 6.x-1.* and 6.x-2.* series, where 6.x-1.2 and 6.x-2.4 are the latest releases.

- Maintainer says both are supported, but 6.x-2.* is recommended (via the new project maintainer UI from http://drupal.org/node/203313).

- A site is running 6.x-1.2.

Currently, update.module tells you:

foo 6.x-1.2            Up to date
Also available:   6.x-2.4

Everything is green/ok, there's no warnings or errors (as expected).

However, it seems like the fact that the maintainer marked the 6.x-2.* series as "recommended" should show up here, too, especially since we already have that info in the .xml files. This case should probably look more like this (still green/ok):

foo 6.x-1.2            Up to date
Recommended version:   6.x-2.4

Do people think this is worth fixing? I'm slightly torn. On the one hand, the maintainer *did* call 6.x-2.* "recommended", so update.module should echo that info. However, it's slightly weird, given the existing update.module UI, for it to say "up to date" but still print out a "Recommended version", since currently, we only print out "Recommended" when the user is some how out of date...

Thoughts?

Thanks,
-Derek

🐛 Bug report
Status

Closed: works as designed

Version

11.0 🔥

Component
Update  →

Last updated about 23 hours ago

  • Maintained by
  • 🇺🇸United States @tedbow
  • 🇺🇸United States @dww
Created by

🇺🇸United States dww

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment over 1 year ago →
    🇬🇧United Kingdom catch

    It's been nearly 18 months since I posted #28, moving to 'needs more info' and will mark 'works as designed' in a few weeks.

  • Status changed to Closed: works as designed 9 months ago
  • Comment 9 months ago →
    🇬🇧United Kingdom catch

    That was more than a few weeks, closing as 'works as designed'. To summarise, if you're on an older branch of a contrib module, and there's a newer branch available, update status will show it as 'also available' instead of 'recommended' - but given both branches are supported, that seems fine. Updating to a newer branch may involve extra steps, so it is worth leaving the tiny bit of friction for people to update to the newer release, given that both wordings are correct as far as the specific site is concerned.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024