From 5dcca3e08868275cf60e3d5ec7921cc71fe3706b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Garc=C3=ADa=20Aubert?=
 <danielgarciaaubert@gmail.com>
Date: Sun, 1 Dec 2019 19:00:27 +0100
Subject: [PATCH] Update 'how to release' document

---
 HOWTO_RELEASE | 18 ------------------
 1 file changed, 18 deletions(-)
 delete mode 100644 HOWTO_RELEASE

diff --git a/HOWTO_RELEASE b/HOWTO_RELEASE
deleted file mode 100644
index 0a398d01..00000000
--- a/HOWTO_RELEASE
+++ /dev/null
@@ -1,18 +0,0 @@
-1. Test (make clean all check), fix if broken before proceeding
-2. Ensure proper version in package.json and package-lock.json
-3. Ensure NEWS section exists for the new version, review it, add release date
-4. If there are modified dependencies in package.json, update them with `npm upgrade {{package_name}}@{{version}}`
-5. Commit package.json, package-lock.json, NEWS
-6. git tag -a Major.Minor.Patch # use NEWS section as content
-7. Stub NEWS/package for next version
-
-Versions:
-
-Bugfix releases increment Patch component of version.
-Feature releases increment Minor and set Patch to zero.
-If backward compatibility is broken, increment Major and
-set to zero Minor and Patch.
-
-Branches named 'b<Major>.<Minor>' are kept for any critical
-fix that might need to be shipped before next feature release
-is ready.