From e3efe4b378268ffcd8547f401d52200e18c10536 Mon Sep 17 00:00:00 2001 From: Charles Kerr Date: Sun, 18 Feb 2018 11:04:21 -0600 Subject: [PATCH] make the table a real table --- docs/tutorial/electron-versioning.md | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/docs/tutorial/electron-versioning.md b/docs/tutorial/electron-versioning.md index cb09c6290ffc..4e580c98a77b 100644 --- a/docs/tutorial/electron-versioning.md +++ b/docs/tutorial/electron-versioning.md @@ -42,17 +42,12 @@ From 2.0 onward, Electron will follow semver. Below is a table explicitly mapping types of changes to their corresponding category of semver (e.g. Major, Minor, Patch). -* **Major Version Increments** - * Chromium version updates - * node.js major version updates - * Electron breaking API changes -* **Minor Version Increments** - * node.js minor version updates - * Electron non-breaking API changes -* **Patch Version Increments** - * node.js patch version updates - * fix-related chromium patches - * Electron bug fixes +| Major Version Increments | Minor Version Increments | Patch Version Increments | +| ------------------------------- | ---------------------------------- | ----------------------------- | +| Electron breaking API changes | Electron non-breaking API changes | Electron bug fixes | +| node.js major version updates | node.js minor version updates | node.js patch version updates | +| Chromium version updates | | fix-related chromium patches | + Note that most chromium updates will be considered breaking. Fixes that can be backported will likely be cherry-picked as patches.