-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Tracking: Library & Pattern Management Issues #51948
Copy link
Copy link
Closed
Labels
Blessed for major releaseCan be iterated during a WordPress beta periodCan be iterated during a WordPress beta period[Feature] PatternsA collection of blocks that can be synced (previously reusable blocks) or unsyncedA collection of blocks that can be synced (previously reusable blocks) or unsynced[Priority] HighUsed to indicate top priority items that need quick attentionUsed to indicate top priority items that need quick attention[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Metadata
Metadata
Assignees
Labels
Blessed for major releaseCan be iterated during a WordPress beta periodCan be iterated during a WordPress beta period[Feature] PatternsA collection of blocks that can be synced (previously reusable blocks) or unsyncedA collection of blocks that can be synced (previously reusable blocks) or unsynced[Priority] HighUsed to indicate top priority items that need quick attentionUsed to indicate top priority items that need quick attention[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Type
Fields
Give feedbackNo fields configured for issues without a type.
The following lists cover known bugs and issues for the current state of the Library and pattern management features. Ideally, we'll get as many of these done as possible before the 6.3 beta 1; however, some work is likely to flow into the beta period, as enabled by the Introducing the Library blessed ticket.
Note: When adding a PR to this tracking issue, make sure it has the
Backport to WP Beta/RClabel on it if it should be included in the WP beta, thanksTodo
In Progress
Completed
Library#51897sync_statustowp_sync_status? - question asked here. Looks like we are too late to consider this as 16.1 already out with existing naming.Closed
Future Follow-ups