DB workflow for DE/AT translations

Created on 30 November 2023, over 1 year ago
Updated 11 May 2024, about 1 year ago

Problem/Motivation

At SplashAwards Germany & Austria on the 10th of November we had a round table and agreed to start the translation of la_eu for la_de and la_at by December. Hence our deadline was to progress on la_eu with the English translation and export the DB on the 30th of November. We build an GitLab automation to export the DB from stage.drupal.eu and stage.drupal.de as pipeline artifacts. But still have some work pending to finish the English translation in code and DB at least.

TL'DR should wait for EN translation before before DE/AT translations
Avoid duplicated efforts in content translation between la_de & la_at

Proposed resolution

  1. Postpone the German/Austrian translation till remaining tasks done
  2. Export la_eu DB with GitLab and import on stage.drupal.de
  3. Work together for DE/AT and export la_de with GitLab again
  4. Branch la_de and la_at DBs, adapt to slangs & go-live with drupal.de

Remaining tasks

DB: Baseline english content
#3397937: Baseline english content

Code: Rebase the setup to english
#3403627: Rebase the setup to english as the base language

Data model changes

No data model change and minimal diverted DBs with shared code :)

🌱 Plan
Status

Fixed

Version

1.0

Component

Miscellaneous

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024