Cheat sheet: Following the work
The 36 terms of this lesson, part by part, with the French word a team in France would use.
1. A history of every change
- Version controlgestion de versions
- a way to record every change to a project's files, so that each change can be found and undone.
- GitGit
- the most common version control tool, which saves each change to a project as a commit.
- GitHubGitHub
- a website that keeps a project and its history online, where a whole team can read and discuss them.
- Commitcommit
- a saved version of the project, with a short message that says what changed and why.
- Commit messagemessage de commit
- the short text saved with each commit, which says what changed and why.
- Historyhistorique
- the list of every commit in a project, with what changed, why, who made it and when.
- Backupsauvegarde
- a copy of a site's data kept in a safe place, to recover it after a loss or an error.
2. From a branch to the live site
- Live site or productionproduction, prod
- the version of a site that visitors see.
- Environmentenvironnement
- one copy of a site in one place, such as the builder's computer, the test copy or the live site.
- Stagingpréproduction, recette
- a test copy of a site that works like the live site, where changes are tried before they go live.
- Branchbranche
- a separate line of work in a project, where a change is prepared without touching the live site.
- Main branchbranche principale
- the version of the project that the live site is built from.
- Preview linklien de prévisualisation
- a private address where you can try one change before it goes live.
- Mergefusionner, merger
- to add the changes of a branch to the main branch, once they're approved.
- Deploydéployer, mettre en prod
- to publish a new version of a site, so that visitors see the changes.
3. Approving a pull request
- Pull requestpull request, demande de fusion
- a change proposed for review before it joins the live site, with the list of what changed.
- Approveapprouver
- to accept a pull request, which means accepting every change in it.
- Reviewerrelecteur, reviewer
- a person who checks a pull request, then approves it or asks for changes.
- Code reviewrevue de code
- a check of a change's code by another developer, before the change is merged.
- Product ownerproduct owner, responsable produit
- the person who decides what a product must do, and who accepts or refuses the work.
- Bug reportrapport de bug
- a message about a bug, with what you did, what you expected, what you saw and the exact error message.
4. Undo or fix
- Incidentincident
- a problem on the live site that harms visitors, such as a payment page that fails.
- Rollbackretour arrière, rollback
- putting the previous version of a site back online, which undoes the whole last update.
- Hotfixcorrectif urgent, hotfix
- a small, urgent fix to a problem on the live site, which goes live as soon as it's checked.
- Smoke testtest de fumée, smoke test
- a quick check of a site's main paths right after an update, such as browsing, the basket and payment.
- Stagingpréproduction, recette
- a test copy of a site that works like the live site, where changes are tried before they go live.
5. Requests, bugs and who owns what
- Issue trackeroutil de suivi des tickets
- a shared list of requests and bugs, with one item for each, such as GitHub Issues, Jira or Trello.
- Issue or ticketticket
- one request or one bug in an issue tracker, with a title, an assignee and a status.
- Assigneeresponsable, assigné
- the person in charge of one issue, who does the work or finds who will do it.
- Statusstatut
- where an issue stands, such as "to do", "in progress" or "done".
- Change requestdemande de modification
- a change to the brief, asked for during the work, which may cost time and money.
- Handoverpassation
- the moment when the builders give the site, its accounts and its documents to the client.
6. What to ask
- Changelogjournal des modifications
- a list, written for people rather than developers, of what changed in each update.
- Rollback planplan de retour arrière
- what the team will do to undo an update if it goes wrong, and how long it will take.
- Four-eyes principleprincipe des quatre yeux
- the rule that no change goes live until a second person has checked it.
- Pull requestpull request, demande de fusion
- a change proposed for review before it joins the live site, with the list of what changed.
Web Technologies · Talking shop · wt.thomasjuldo.com/course/talking-shop/following-the-work