[policy, no patch] Mark Package Manager as a beta stability core module

I think all that needs to happen here is that the RMs have to agree that beta stability requirements have been met, and then we update the documentation to match.

I assume the answer is no, but wanted to ask: I assume the rebranding of auto updates to “Update Manager” per 📌 [policy] Core module machine name and UI labeling for Automatic Updates Active and others doesn’t impact package_manager at all, right? There are no functions that might need renaming, correct?

Thanks,
-Derek

Correct.

Groovy, thanks.

Where might one review the list of beta blockers, outstanding stable blockers, etc?

🌱 Drupal 10 Core Roadmap for Automatic Updates Active is the main plan issue.

I'd personally be happier here if the issue summary on 🌱 Drupal 10 Core Roadmap for Automatic Updates Active was a bit clearer. I tried to re-organise it a bit this past week, but it's still hard to see what the stable blocking issues are or aren't, and some issues are open but still in the beta blockers list - I duplicated one to the stable list just now.