[FR] Localize blue-green deployment
#2261
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Stéphane Este-Gracias <[email protected]>
✅ Deploy Preview for cncfglossary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
sestegra
changed the title
blue-green deployment
Signed-off-by: Stéphane Este-Gracias <[email protected]>
… dev-fr-blue-green
sestegra
requested review from
caniszczyk,
CathPag,
JasonMorgan,
seokho-son,
iamNoah1,
jihoon-seo and
nate-double-u
as code owners
content/fr/blue-green-deployment.md
Outdated
| ## Quel en est l'utilité | ||
|
|
||
| Le déploiement bleu/vert est une stratégie appropriée pour les logiciels non Cloud Natives qui doivent être mis à jour avec un temps d'arrêt minimal. | ||
| Cependant, son utilisation est normalement un "signe" que le logiciel hérité doit être réingénierisé afin que les composants puissent être mis à jour individuellement. |
There was a problem hiding this comment.
Je trouve que réingénierisé est correct mais un peu jargoneux. Repensé, ou refondu, ou un truc comme ça me parait plus simple.
En plus dans la vraie vie, personne ne dis réingénierisé, tout le monde dit réingénieré même si c'est incorrect et un anglicisme 😁
There was a problem hiding this comment.
Je suis assez d'accord avec @guillaumebernard84.
J'proposerai bien "redévelopper" ou "réorganiser"
There was a problem hiding this comment.
J'ai choise "redéveloppé"
Krast76
requested changes
Sep 3, 2023
content/fr/blue-green-deployment.md
Outdated
| ## Quel en est l'utilité | ||
|
|
||
| Le déploiement bleu/vert est une stratégie appropriée pour les logiciels non Cloud Natives qui doivent être mis à jour avec un temps d'arrêt minimal. | ||
| Cependant, son utilisation est normalement un "signe" que le logiciel hérité doit être réingénierisé afin que les composants puissent être mis à jour individuellement. |
There was a problem hiding this comment.
Je suis assez d'accord avec @guillaumebernard84.
J'proposerai bien "redévelopper" ou "réorganiser"
jihoon-seo
removed request for
caniszczyk,
nate-double-u,
JasonMorgan,
seokho-son,
iamNoah1,
jihoon-seo and
CathPag
Signed-off-by: Stéphane Este-Gracias <[email protected]>
Signed-off-by: Stéphane Este-Gracias <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Localize
blue-green deploymentRelated issue number or link (ex:
resolves #issue-number)resolves #2260
Checklist before opening this PR (put
xin the checkboxes)git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to yourgitconfigby runninggit config --global alias.ci "commit -s".