Skip to content
Snippets Groups Projects
  1. Sep 04, 2019
  2. Sep 02, 2019
  3. Aug 30, 2019
  4. Aug 29, 2019
  5. Aug 22, 2019
  6. Aug 02, 2019
  7. Jul 29, 2019
  8. Jul 11, 2019
  9. Jul 10, 2019
  10. May 23, 2019
  11. May 22, 2019
  12. May 17, 2019
  13. May 16, 2019
  14. May 03, 2019
  15. Apr 30, 2019
  16. Apr 10, 2019
  17. Apr 05, 2019
  18. Jan 29, 2019
  19. Jan 28, 2019
  20. Jan 24, 2019
    • erwan's avatar
      Automate version numbering using Semantic Versionning (semantic-release-gitlab) · 9beabcb2
      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.
      6.100.1
      9beabcb2
Loading