- First commit to issue fork.
- last update
over 1 year ago 29,378 pass - @ranjit1032002 opened merge request.
- last update
over 1 year ago 29,378 pass - Status changed to Needs review
over 1 year ago 5:52am 5 May 2023 - ๐ฎ๐ณIndia Ranjit1032002
Created MR!3935 for the issue mentioned, please review.
Thank You. - Status changed to Needs work
over 1 year ago 6:58pm 5 May 2023 - ๐บ๐ธUnited States smustgrave
Language seems like someone is speaking directly to me vs announcing a description.
- ๐ณ๐ฟNew Zealand quietone
@Ranjit1032002, thank you for making an MR. However, next time make sure you are changing the correct string. The string changed in the MR is for unsupported releases not revoked as is stated in the issue summary.
In my opinion, the existing test
Disabling everything included in this release or upgrading is strongly recommended!'
handles the case where there is no update because it says to 'disable everything'. The suggested 'upgrading' is an option only. I will ask in #bugsmash and #ux.This is about the UI, so tagging.
@smustgrave, what documentation needs to be changed in this issue?
- ๐บ๐ธUnited States benjifisher Boston area
We discussed this issue briefly at ๐ Drupal Usability Meeting 2023-08-04 Needs work . That issue will have a link to a recording of the meeting.
For the record, the attendees at today's usability meeting were @AaronMcHale, @Emma Horrell, @benjifisher, @rkoller, @simohell, and @worldlinemine.
We decided that we did not have enough context to make an informed recommendation. How does a release get "revoked"? Does that mean unpublished, or is it specifically when the maintainer marks it as unsupported?
With that caveat, we tend to agree with #9.
Besides the question raised in this issue, the current message has some other problems. It refers to "disabling" a module, which is only possible in Drupal 7 and earlier.