Deprecate the Drupal 7 Releases and Dev branch

Problem/Motivation

Thread 2 of meeting 9/15/2021

@chrisfromredfin

I would like to discuss whether or not we should archive some of the Drupal 7 stuff on the project_browser page. Right now about 10% of the page is dedicated to us as an initiative and 90% of it is dedicated to an older project with 10 active installs. Should we remove the D7 release as a recommended release? Should we use AmyJune's template to write our own description where we eat our own dog food? Would anyone be willing to tackle this? It can always be a work in progress. So, looking for discussion on whether or not we should and someone to help rewrite our project description page.

@drumm

the server side was never completed or deployed, so the D7 version doesn’t need any non-trivial mention.

So, safe to say, since the Drupal 7 version has no way of working, the 10 installs won't be affected by marking those releases as unsupported and unrecommended.

Steps to reproduce

Visit the project page of this module.

Proposed resolution

1. On the Edit > Releases form, uncheck Supported and Recommended on all the Drupal 7 branches
2. On the Edit > Releases form, check Supported and Recommended on the Drupal 9 branch(es)

I will create a separate issue for "Remove or rewrite the Drupal 7 and 1.x copy on the Project page".

Remaining tasks

1, 2.

User interface changes

N/A

API changes

N/A

Data model changes

N/A