[ISSUE HAS BEEN MOVED] Phase 1 resend
We're re-sending Phase 1 files in order to:
- capture updates introduced to the JA target files and TM after the files were set to complete
- capture the latest styleguide and terminology updates that were flagged during this first round of Phase 1 through our AI script updates
- there will be some net new content as the source files had been updated while we were translating them so we will capture those EN updates too. Every time an English file is sent for translation we always send the most up to date version of the file.
- the front matter description field is in scope now so we will get Phase 1 files description translated in this batch too
- we're generating the anchor IDs automatically on the EN files through Argo. We're using this batch to get that feature rolling for the first time after testing it on Argo's clone server.
A new tab named Phase 1.2 has been added to the content prioritization spreadsheet to keep track of the new translation requests. Pasting it here too for visibility.
- GITTECHA-37
- GITTECHA-38
- GITTECHA-39
- GITTECHA-40
- GITTECHA-41
- GITTECHA-42
- GITTECHA-43
- GITTECHA-44
- GITTECHA-45
- GITTECHA-46
Translation MRs
- gitlab-runner!30 (closed)
- https://gitlab.com/gitlab-com/localization/tech-docs-forked-projects/prod/gitlab/-/merge_requests/96
- gitlab-chart!17 (merged)
- omnibus-gitlab!23 (closed)
- gitlab-operator!21 (closed)
- gitlab-runner!31 (closed)
- https://gitlab.com/gitlab-com/localization/tech-docs-forked-projects/prod/gitlab/-/merge_requests/98
- https://gitlab.com/gitlab-com/localization/tech-docs-forked-projects/prod/gitlab/-/merge_requests/99
- https://gitlab.com/gitlab-com/localization/tech-docs-forked-projects/prod/gitlab/-/merge_requests/97
- gitlab-docs!29 (merged)
GITTECHA-45
This request generated two identical Phrase projects due to a timeout issue.
Argo has a 15 minute timeout configured for steps. If it takes longer than that to execute, it retries the step. The Create Phrase Project step took 15 minutes and 30 seconds to execute, so it retried it. Phrase just took 15 minutes to process all the files we uploaded via it’s Async API.This setting is set to 15 minutes to retry steps that have died silently, but 15 is too aggressive. I suggest we set it to 60 minutes. If a step has died silently, waiting an extra 45 minutes to have it auto retry isn’t too costly, but it will nearly eliminate the risk of accidentally creating multiple Projects in Phase
The correct Phrase project where target files should be delivered is https://us.cloud.memsource.com/web/project2/show/kugNZ7M9uhEvcJqKJR7Xv3
