- Sep 04, 2019
-
-
erwan authored
- Sep 02, 2019
- Aug 30, 2019
-
-
erwan authored
-
- Aug 29, 2019
- Aug 22, 2019
-
-
erwan authored
-
- Aug 02, 2019
-
- Jul 29, 2019
-
-
erwan authored
-
- Jul 11, 2019
-
- Jul 10, 2019
-
- May 23, 2019
-
-
erwan authored
-
- May 22, 2019
-
-
erwan authored
- May 17, 2019
- May 16, 2019
- May 03, 2019
-
-
erwan authored
-
Pascal Raymond authored
-
Pascal Raymond authored
-
- Apr 30, 2019
- Apr 10, 2019
-
-
erwan authored
Rationale: a step to make time traveling work correctly.
-
- Apr 05, 2019
- Jan 29, 2019
- Jan 28, 2019
-
-
erwan authored
-
- Jan 24, 2019
-
-
erwan authored
https://www.npmjs.com/package/semantic-release-gitlab from https://semver.org/ : Given a version number MAJOR.MINOR.PATCH, increment the: - MAJOR version when you make incompatible API changes, - MINOR version when you add functionality in a backwards-compatible manner, and - PATCH version when you make backwards-compatible bug fixes. For MAJOR, choosing 6 is obvious. From Minor it's not clear. This number is supposed to reflect the number of add functuionnality, so starting at 0 is not great. The current version is 1.762, but starting at 762 would be wrong too, as most do not deals with new functionnalyties. In a ideal word, I should use the log and tag every commit tha deals with a new functionnalyty, but there is a lot of commits (762). Hence I,'ve decided to choose 100.
-