Voting starts in March for the Drupal Association Board election.
Follow-up towhich adds a hash to configuration files. We need to provide a upgrade path for existing sites.
Discussed with @catch and @Gábor Hojtsy. We agreed that the upgrade path should:
- check all active config and if name does not match - do not add hash
- If name matches but has custom config translations - do NOT add hash
- Otherwise add hash.
This way we don't get data loss and most sites will get localisations for default config.
User interface changes
Data model changes
Existing configuration entities created through the installer have a default_config_hash key set.