Term extraction: Release your application - candidate list (#927) · Issues · GitLab.com / localization / Docs Site Localization

Term extraction: Release your application - candidate list

#### Context Part of the EN baseline term extraction (#916+). The hub and sub-pages of the [Release your application](https://docs.gitlab.com/topics/release_your_application/) section were scanned for terminology candidates. Pages processed: - Hub: `doc/topics/release_your_application.md` - `doc/ci/environments/_index.md` - `doc/ci/environments/deployments.md` - `doc/ci/environments/deployment_safety.md` - `doc/ci/environments/protected_environments.md` - `doc/ci/environments/incremental_rollouts.md` - `doc/ci/environments/deployment_approvals.md` - `doc/ci/resource_groups/_index.md` - `doc/user/project/releases/_index.md` - `doc/user/project/releases/release_fields.md` - `doc/user/project/releases/release_evidence.md` - `doc/user/packages/_index.md` - `doc/topics/autodevops/_index.md` - `doc/topics/autodevops/stages.md` - `doc/ci/cloud_deployment/_index.md` - `doc/cloud_seed/_index.md` **Scope note:** extraction was limited to the section `_index` pages listed above — one level below the hub. Sub-pages of those sections were not scanned. Additional scope needs to be defined for a deeper pass. Each candidate was evaluated using the 8-criteria framework (2+ required) plus the translation-risk test: 1=Terminologization, 2=Confusability, 3=Specialization, 4=Frequency, 5=Visibility, 6=Novelty, 7=System relationships, 8=Standardization potential. Terms already covered in pilot TBX, #923, and #926 are not repeated here. @maud-L , before we proceed to writing TBX briefs and entries, your guidance is needed on: 1. Which terms should be included vs. skipped 2. For flagged Quickterm situations in the Notes column — add a comment or resolution #### How to review 1. **Read the table** 2. **Work through the checklist at the bottom** - check the box to include a term in the TBX, leave it unchecked to skip it. 3. **Add an inline comment on a checklist line** if you have a question, a different FR suggestion, or a reason for skipping. #### Extracted terms <table> <tr> <th>Term</th> <th>File(s)</th> <th>Count</th> <th>In Quickterm</th> <th>FR (from Quickterm)</th> <th>Notes</th> </tr> <tr> <td>deployment tier</td> <td>doc/ci/environments/_index.md, doc/ci/environments/protected_environments.md</td> <td>~15</td> <td>No</td> <td></td> <td>GitLab classification of environments (development/testing/staging/production/other). 'Tier' also means pricing level — high false-friend risk. Criteria: 1,2,3,7,8.</td> </tr> <tr> <td>deployment rollback</td> <td>doc/ci/environments/deployments.md, doc/ci/environments/deployment_safety.md, doc/ci/environments/_index.md</td> <td>~18</td> <td>No</td> <td></td> <td>In GitLab, a rollback creates a new deployment pointing to an older commit — not a simple undo. FR risk: retour arrière vs. restauration vs. borrowed rollback. Note: Quickterm has a conflict on standalone rollback (one Preferred, one Forbidden entry). Criteria: 1,2,3,4,5,7.</td> </tr> <tr> <td>deploy freeze</td> <td>doc/ci/environments/deployment_safety.md, doc/user/project/releases/_index.md</td> <td>~12</td> <td>Yes</td> <td>gel du déploiement (Preferred)</td> <td>Named GitLab concept: configured time window blocking all deployments. Also appears as <code>deployment freeze window</code> and <code>freeze period</code> — three synonymous forms need normalization in FR. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>resource group</td> <td>doc/ci/resource_groups/_index.md, doc/ci/environments/deployment_safety.md</td> <td>~45</td> <td>No</td> <td></td> <td>GitLab CI/CD keyword controlling job concurrency per deployment target. Must not be confused with cloud provider 'resource group' (Azure/GCP). High confusability, high frequency. Criteria: 1,2,3,4,5,7,8.</td> </tr> <tr> <td>process mode</td> <td>doc/ci/resource_groups/_index.md</td> <td>~20</td> <td>No</td> <td></td> <td>Execution ordering policy of a resource group: <code>unordered</code>, <code>oldest_first</code>, <code>newest_first</code>, <code>newest_ready_first</code>. No equivalent in standard DevOps terminology. FR: mode de traitement vs. mode d'exécution — inconsistency risk. Part of resource group system. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>deployment job</td> <td>doc/ci/environments/deployments.md, doc/ci/environments/_index.md, doc/ci/environments/deployment_safety.md</td> <td>~30</td> <td>Yes (no FR)</td> <td></td> <td>A CI/CD job that uses the <code>environment</code> keyword to deploy to an environment. Has special properties (triggers deployment records, interacts with protected environments). Distinct from a regular CI/CD job. Entry in Quickterm, FR empty. Criteria: 1,2,3,4,5,7,8.</td> </tr> <tr> <td>approval rule</td> <td>doc/ci/environments/protected_environments.md, doc/ci/environments/deployment_approvals.md</td> <td>~15</td> <td>Yes</td> <td>règle d'approbation (Preferred)</td> <td>Configured rule specifying who must approve and how many approvals are required before a deployment proceeds. Distinct from MR approval rules — same phrase, different system. FR confirmed by Quickterm. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>group-level protected environment</td> <td>doc/ci/environments/protected_environments.md</td> <td>~12</td> <td>No</td> <td></td> <td>A protected environment enforced at group level (vs. project level), using deployment tiers as names. Distinct configuration object. FR: long compound requiring consistent treatment alongside project-level protected environment. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>deployment-only access</td> <td>doc/ci/environments/protected_environments.md</td> <td>~6</td> <td>No</td> <td></td> <td>Access grant allowing deployment to a protected environment but not pushing/merging code. Named permission model. FR: accès déploiement uniquement is awkward — needs a standardized form. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>release evidence</td> <td>doc/user/project/releases/release_evidence.md, doc/user/project/releases/_index.md</td> <td>~25</td> <td>Yes</td> <td>preuve de déploiement (Preferred)</td> <td>Automated JSON snapshot captured at release creation for compliance/audit. FR false-friend risk: preuve (legal), justificatif, attestation — Quickterm confirms preuve de déploiement. Criteria: 1,2,3,5,6,7,8.</td> </tr> <tr> <td>release asset</td> <td>doc/user/project/releases/release_fields.md, doc/user/project/releases/_index.md</td> <td>~20</td> <td>Yes</td> <td>ressource associée à une version de release (Preferred)</td> <td>Files or links attached to a GitLab Release. 'Asset' is a false friend in FR (actif = financial asset). Quickterm FR is unusually long — worth validating. Criteria: 1,2,3,4,5,7,8.</td> </tr> <tr> <td>link type</td> <td>doc/user/project/releases/release_fields.md</td> <td>~8</td> <td>No</td> <td></td> <td>Classification of a release asset link: <code>runbook</code>, <code>package</code>, <code>image</code>, <code>other</code>. FR: type de lien could be read as 'type of hyperlink' — the compound is ambiguous. Part of the release asset system. Criteria: 1,2,3,7,8.</td> </tr> <tr> <td>release notes</td> <td>doc/user/project/releases/release_fields.md, doc/user/project/releases/_index.md</td> <td>~8</td> <td>Yes</td> <td>notes de version (Preferred)</td> <td>The description field of a GitLab Release. FR notes de version vs. notes de publication inconsistency is documented in FR localization communities — Quickterm confirms notes de version. Criteria: 1,2,3,4,5,8.</td> </tr> <tr> <td>release permalink</td> <td>doc/user/project/releases/_index.md</td> <td>~4</td> <td>No</td> <td></td> <td>Permanent URL always redirecting to the latest release. Lien permanent is the standard FR form. Not in Quickterm. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>blue-green deployment</td> <td>doc/ci/environments/incremental_rollouts.md</td> <td>~6</td> <td>Yes</td> <td>déploiement bleu/vert (Preferred)</td> <td>Deployment strategy using two parallel identical environments, switching traffic at cutover. Quickterm uses slash: bleu/vert. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>timed rollout</td> <td>doc/ci/environments/incremental_rollouts.md</td> <td>~10</td> <td>No</td> <td></td> <td>Incremental rollout variant where each tranche is released after an automatic delay. Paired with manual rollout — both must be translated consistently. FR: déploiement progressif minuté vs. déploiement différé. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>manual rollout</td> <td>doc/ci/environments/incremental_rollouts.md</td> <td>~8</td> <td>No</td> <td></td> <td>Incremental rollout variant where each tranche is triggered manually. Directly paired with timed rollout — opposite control model. FR: déploiement manuel is likely but must be consistent with timed rollout treatment. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>Auto Rollback</td> <td>doc/ci/environments/_index.md</td> <td>~5</td> <td>No</td> <td></td> <td>GitLab Ultimate feature that automatically triggers a rollback when a critical alert fires. Named feature — distinct from manual deployment rollback. Not in Quickterm. Criteria: 1,2,3,5,6,7.</td> </tr> <tr> <td>tranche</td> <td>doc/ci/environments/incremental_rollouts.md</td> <td>~4</td> <td>No</td> <td></td> <td>A percentage subset of Kubernetes pods targeted in one incremental rollout step. The word is French in origin but used as an English technical term — FR translator may not recognize it and translate it differently. Criteria: 1,2,3,7.</td> </tr> <tr> <td>generic package</td> <td>doc/user/project/releases/release_fields.md, doc/user/packages/_index.md</td> <td>~10</td> <td>No</td> <td></td> <td>A format-agnostic binary storage package type. 'Generic' as a type name is maximally confusable — FR générique risks losing the technical specificity of this package format. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>dependency proxy</td> <td>doc/user/packages/_index.md</td> <td>~4</td> <td>Yes</td> <td>proxy de dépendances (Preferred)</td> <td>GitLab pull-through cache for upstream container images. Named feature. FR confirmed by Quickterm. Criteria: 1,2,3,5,7,8.</td> </tr> <tr> <td>virtual registry</td> <td>doc/user/packages/_index.md</td> <td>~3</td> <td>No</td> <td></td> <td>New GitLab caching/proxy layer for external registries. Distinct from container/package registry. FR: registre virtuel is a calque needing validation. Criteria: 1,2,3,6,7.</td> </tr> <tr> <td>buildpack</td> <td>doc/topics/autodevops/stages.md, doc/topics/autodevops/_index.md</td> <td>~8</td> <td>No</td> <td></td> <td>Detection/build mechanism used by Auto DevOps. Typically kept as buildpack (DNT) in FR tech docs — translator note needed. Criteria: 1,2,3,5.</td> </tr> <tr> <td>service account</td> <td>doc/cloud_seed/_index.md, doc/ci/cloud_deployment/_index.md</td> <td>~5</td> <td>Yes</td> <td>compte de service (Preferred)</td> <td>Non-human authentication identity for cloud deployment. FR confirmed by Quickterm. Criteria: 1,2,3,7.</td> </tr> </table> #### Terms excluded after applying extraction criteria - `static environment / dynamic environment` — removed: 'environnement' is unambiguous in context; the static/dynamic distinction does not create translation risk a translator cannot resolve - `environment` — generic word - `deployment` — generic word - `continuous delivery / continuous deployment` — industry-standard terms with well-established FR equivalents; Quickterm confirms livraison continue / déploiement continu — no translation risk remaining - `rollback (standalone)` — conflict in Quickterm noted in #931; deployment rollback (the GitLab-specific compound) is included above - `annotated tag` — Git concept, not GitLab-specific; étiquette annotée is confirmed in Quickterm - `release (standalone)` — already in #923 - `protected environment` — already in #923 - `deployment approval` — already in #923 - `feature flag` — already in #923 - `canary deployment` — already in #926 - `incremental rollout` — already in #923 - `Auto DevOps` — GitLab product name — excluded per rules - `Cloud Native Buildpack` — CNCF proper noun — third-party standard - `CloudFormation, ECS, GKE, Cloud Run` — third-party product names #### Review checklist  - [ ] deployment tier - [ ] deployment rollback - [ ] deploy freeze - [ ] resource group - [ ] process mode - [ ] deployment job - [ ] approval rule - [ ] group-level protected environment - [ ] deployment-only access - [ ] release evidence - [ ] release asset - [ ] link type - [ ] release notes - [ ] release permalink - [ ] blue-green deployment - [ ] timed rollout - [ ] manual rollout - [ ] Auto Rollback - [ ] tranche - [ ] generic package - [ ] dependency proxy - [ ] virtual registry - [ ] buildpack - [ ] service account

issue