- 🇺🇸United States xjm
Updating title to include that alternate potential resolution. Are there also places that the decision that the API is stable should be documented in the PM codebase and/or the handbook?
- 🇺🇸United States xjm
The other thing is that Package Manager really does not correspond at all to normal expectations of a beta module (which generally means exposed to end users for testing within the application). The module is still marked hidden (and definitely should remain so!!).
An alternate course of action that I discussed with @phenaproxima in Slack is to avoid the confusing "What is beta really?" question that comes with wildly divergent expectations, and instead have a release note targeting developers something like:
The hidden, experimental Package Manager module allows Automatic Updates and Project Browser to be tested so that they can eventually be added to future versions of Drupal core. Package Manager is now considered API-stable, and future API changes will be backwards-compatible, so contributed module developers can now rely on its APIs.
(That with the appropriate things linked as per the 11.1.0 release notes.)
Or something, please feel free to propose improvements.
- 🇺🇸United States xjm
Sorry about the status wars, @smustgrave, but I think we still need review of the IS updates @catch requested for this to be RTBC.
I think we would need a lot more clarification/caveats for users about the signing and infra work being deferred to stable-blocking.
I have concerns with this sentence:
so it is now considered safe to rely on this module and build other projects on top of it
The only thing that is safe is the stability of the API. The packages are not actually being signed or validated. This seems misleading in a bad way. :)
Hello,
I've created three alternatives and modified the text part. I prefer the first one. Would be glad to hear from you.
Will create the MR once the logo is finalised. Moving to NR.
Attaching the PNG and zip for the SVG formats as per the request in #7.
Thanks
