Quantcast
Channel: Issues for Drupal core
Viewing all articles
Browse latest Browse all 298231

Mark Workspaces as a stable core module

$
0
0

Blocked by issues tagged WI critical

Problem/Motivation

Once the roadmap for the Workspaces is complete, we'll need sign-offs on the final state as well as a patch to actually mark the module stable.

Proposed resolution

  • Add to or update MAINTAINERS.txt entry for the module as needed.
  • Remove the experimental module designation from workspaces.info.yml.
  • Remove the @internal from Workspaces APIs intended to be public.
  • Replace the @internal text for APIs that are intended to remain internal even after the module is stable with explanations of why the code in question is internal (e.g., specific categories from https://www.drupal.org/core/d8-bc-policy, etc.)
  • Copy CSS and templates to Stable or Classy as appropriate.

Remaining tasks

Release management checklist

  1. Security
  2. Data integrity
  3. Impact on stable functionality

    Integrations

    • All revisionable and publishable entity types (Node, Taxonomy term, Custom menu link, Media, Path alias)
    • Content Moderation
    • REST and JSON:API
    • Multilingual functionality
    • Other areas?
  4. Maintenance and technical debt
    • Active maintainers listed with their agreement to maintainer roles documented
    • Issue queue review
  5. API definition and BC policy
  6. Core gates
    • Usability
    • Accessibility
    • Testing
    • Documentation
      • API documentation and definitition
      • Module name and description
      • hook_help()
      • Handbook page
    • Performance

Release notes snippet


Viewing all articles
Browse latest Browse all 298231

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>