Problem/Motivation

We need an upgrade path from 7.x for the core Locale module.

Remaining Tasks

Write a migration, with a test, that moves variables maintained by Locale into configuration.

Comments

svendecabooter’s picture

svendecabooter
he/him
Primary language Dutch
Location Gent
commented

I guess this is being tackled in child issues of #2208401: [META] Remaining multilingual migration paths?

steinmb’s picture

steinmb commented
Parent issue: » #2208401: [META] Remaining multilingual migration paths

Not in the meta issue it self but in all those child issues by added to it. Not sure if there is settings in locale that need special migration, if yes, I'm pretty sure it will be done in here.

quietone’s picture

quietone commented
Issue tags: +migrate-d7-d8

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

With #2353709: Variables to config: language.types [d7] and #2225293: Migrate D6 and D7 language negotiation settings following up after #2130307: Variable to config: language.negotiation [d7] and #2353761: Variable to config: locale.settings [d7], what else is left here? I assume we do NOT want to migrate the string translations themselves. We are migrating i18n strings (also stored in the locale tables) in individual issues like #2225717: Add config translation support to migrations and implement for Drupal 6 user profile fields but do we want to keep the string translations? Drupal 8 should download those for the modules/themes installed, so only custom code may be concerned here. OTOH we cannot tell which strings came from custom code and this is a fantastic opportunity for people to clean up old cruft.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Related issues: +#2456259: [META] Drupal 7 to Drupal 8 Migration path

Adding the main D7-D8 issue as a related issue.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

I still hold my opinion/question from #6.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Closed (duplicate)

In response to Gabor's question - silence implies consent (that there's nothing left to do here, with the doable parts already done elsewhere)?