The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.https://drupal.org/project/issues/search/drupal?status%5B%5D=1&status%5B...
Beta targets
https://drupal.org/project/issues/search/drupal?project_issue_followers=...
Priority for the first beta
- #2247257: Use of UUIDs in image style config file for effect ids
- (?) #2140511: Configuration file name collisions silently ignored for default configuration
- (jessebeach) #2235363: Document config dependencies
Nice-to-have or do later
- (?) #2205527: Move configuration import lock to lock.persistent service since a lock can not exist beyond a single request
- (?) #1880766: Preload configuration objects
- (?) #2212151: Document/test updating active configuration based on API changes (i.e. plugins)
- (?) #2089757: Auto generate routing entries for entities based on an 'admin_path' and 'admin_permission' annotation
- (?) #2090115: Don't install a module when its default configuration has unmet dependencies
What we've got done already!
Beta blockers
- (tim.plunkett) #2248151: Configurable plugins can not control instance-specific config dependencies
- (damiankloip) #2216071: Views plugins need a way to store additional dependencies
- (Gábor Hojtsy) #2234623: Move language add logic out of language_save()
- (alexpott) #2198429: Make deleted fields work with config synch
- (jessebeach) #1067408: Themes do not have an installation status
- (Berdir) #2124535: Prevent secondary configuration creates and deletes from breaking the ConfigImporter
- (alexpott) #2238069: Create a way to add steps to configuration sync
- (alexpott) #2199483: Provide a default config_prefix based on entity type ID and provider
- (alexpott) #2080823: Create API to discover config entities' soft dependencies and use this to present a confirm form on module uninstall
- (alexpott) #2004370: Batch the configuration synchronisation process
- (alexpott) #2030073: Config cannot be imported in order for dependencies
- (alexpott) #2232275: System menu blocks need to be able to depend on their menu entities
- (alexpott) #1808248: Add a separate module install/uninstall step to the config import process
- (Gábor Hojtsy) #2201437: [META-1] Config overrides and language
- (Eli-T) #2215413: Split the Config class into StorableConfigBase and ConfigBase. Make ThemeSettings inherit from ConfigBase.
- (Gábor Hojtsy) #2215503: Use services instead of event subscribers for config module overrides
- (Gábor Hojtsy) #2219499: Generalize language config override responsibility
- (Gábor Hojtsy) #2175917: Clean up configuration system events
- (xjm) #2110615: Do not ship with default UUIDs
- (xjm) #1709960: declare a maximum length for entity and bundle machine names
- (alexpott) #2224873: Handle a config entity with the same name but different UUID being imported
- (alexpott) #2232597: FieldConfig does not depend on the module the provides the entity type
- (jessebeach) #2218655: Core expects $theme.settings default config file to exist
- (?) #2161591: Change default active config from file storage to DB storage
- (alexpott) #2236553: Config import validation needs to be able to list multiple issues and the messages should be translatable
- (alexpott) #1740378: Implement renames in the import cycle
- (alexpott) #2245729: Add missing configuration schema in Color component
- (?) #2245721: Add missing configuration schema in language component
- (alexpott) #2259525: system.action.user_add_role_action.ROLE_ID does not match any config schema
- (alexpott) #2261677: Entity displays need to depend on the entity provider is there is no bundle entity type.
- (alexpott) #2262861: Add concept of collections to config storages
- (Gábor Hojtsy) #2224887: Language configuration overrides should have their own storage
- (jessebeach) #2228763: Create a comment-type config entity and use that as comment bundles, require selection in field settings form
- (alexpott) #2224761: Add a generic way to add third party configuration on configuration entities and implement for field configuration
Beta targets
- (mtift) #2108813: Add fancier config import/export test scenario
- (?) #2216961: Document Config, ConfigBase, and StorableConfigBase
- (xjm) #2233787: Move default configuration into extension/config/install to clarify its purpose
- (?) #2216529: Fill in topic/@defgroup docs for Config and State System
- (?) #2228763: Create a comment-type config entity and use that as comment bundles, require selection in field settings form
- (?) #2260457: Allow config entities to remove dependent configuration keys when dependencies are deleted due to module uninstall
- (mtift) #2148199: Use snapshot to warn users if the configuration has changed since last import
Comments
Comment #1
xjmAs of today, @alexpott recommended the following order for next steps:
Comment #2
xjmComment #3
catchComment #4
Anonymous (not verified) commented#1 looks sane. which sprint is referred to in 'Sprint Order'?
Comment #8
xjm@alexpott, @mtift, @GaborHojtsy, and myself reviewed all of our current beta blockers yesterday. Updated plan in the summary.
The name in parentheses for each issue is the issue owner.
Comment #9
xjmAlso, several issues currently tagged "beta blocker" are not listed and are being de-scoped from the beta. @alexpott is following up on these issues individually.
Comment #10
xjmComment #11
Anonymous (not verified) commentedComment #12
alexpottWe forgot about renames.
Comment #13
xjmComment #14
xjmComment #15
alexpottComment #16
xjmComment #17
xjmComment #18
alexpottComment #19
alexpottComment #20
alexpottComment #21
xjmWhere does #2198429: Make deleted fields work with config synch go?
Comment #22
alexpottComment #23
xjmComment #24
alexpott#1740378: Implement renames in the import cycle is dependent on #2080823: Create API to discover config entities' soft dependencies and use this to present a confirm form on module uninstall
Comment #25
xjmComment #26
xjmComment #27
jessebeach commentedComment #28
xjmComment #29
jessebeach commentedComment #30
alexpottComment #31
alexpottComment #32
alexpottComment #33
alexpottComment #34
xjmComment #35
Anonymous (not verified) commentedComment #36
jessebeach commentedComment #37
alexpottComment #38
alexpottComment #39
alexpottComment #40
jessebeach commentedComment #41
jessebeach commentedComment #42
xjm#2161591: Change default active config from file storage to DB storage is likely to end up being a beta blocker, but doesn't block any other CMI work AFAIK, though it would have to be made to work with #2224887: Language configuration overrides should have their own storage I think. Adding it to the list so that it stays on our radar.
Comment #43
xjmComment #44
xjmComment #45
xjmComment #46
xjmComment #47
xjmComment #48
xjmComment #49
alexpottComment #50
alexpottComment #51
alexpottComment #52
alexpottComment #53
xjmAh, that's much easier to read. :)
Comment #54
sunFWIW, if you append @ after the issue number in the issue link filter macro, then the output includes who is assigned; e.g.:
#1067408: Themes do not have an installation status Assigned to: sun
cf. https://drupal.org/filter/tips#filter-filter_project_issue_link
Comment #55
xjmThe name in parentheses is the beta blocker owner in our beta release management, not necessarily the same as the assignee.
Comment #56
alexpottComment #57
xjmComment #58
xjmComment #59
xjmComment #60
xjmComment #61
xjmComment #62
xjmComment #63
alexpottComment #64
alexpottComment #65
xjmComment #66
xjmComment #67
xjmComment #68
xjmComment #69
xjmRemoving the beta blocker tag, since this itself is not actually blocking the beta and we know where to find it. ;) Unlike some other metas where the problem space is not well-defined, issues only make it onto this list once they're already tagged as beta blockers themselves.
Leaving at critical for visibility, because it is.
Comment #70
alexpottComment #71
xjm/train
Comment #72
xjmComment #73
alexpottComment #74
xjmComment #75
alexpottComment #76
xjmComment #77
xjmComment #78
xjmComment #79
xjmComment #80
xjmComment #81
jessebeach commented#2232605: Themes cannot be uninstalled got downgraded from beta blocker status.
Comment #82
alexpottComment #83
alexpottComment #84
alexpottComment #85
alexpottComment #86
alexpottComment #87
alexpottComment #88
xjmComment #89
jessebeach commentedComment #90
alexpottComment #91
alexpottComment #92
alexpottComment #93
alexpottOops
Comment #94
alexpottComment #95
xjmComment #96
xjmI've left this open for our beta target issues.
Comment #97
xjmTime to call this fixed.
See you in #2345225: [meta-0] CMI path to release!
Comment #98
xjm