4 Comments
Guest *Tal Galili* @ 2013-06-29 12:53:52 originally posted:
Hi Yihui,
I wanted to thank you for a good post. I will adopt your versioning scheme from now on.
Best,
Tal
Guest *Karthik Ram* @ 2014-02-17 22:33:28 originally posted:
Hi Yihui,
Wondering about rules 5 and 6, especially this part (same thing applies to 2.0 vs 1.0). At some point, as I keep adding features, I am going to go from 1.9 to 2.0 and this may not necessarily be due to a big feature or API change (something that will affect backward compatibility). It's just that I've run out of numbers under version 1. What then? Do I just continue on? Sorry if I missed something really obvious here.
The version after 1.9 is 1.10 if there are no significant API changes. Then v1.11, v1.12, ...
Originally posted on 2014-02-18 03:03:06
Guest *Karthik Ram* @ 2014-02-18 03:09:33 originally posted:
Perfect, thanks
Guest *Giovanni Colitti* @ 2022-04-12 21:59:54 originally posted:
By default Git does not sort tags based on semantic version number. You can use the following to change how git tag -l will sort tags:
git config --global tag.sort -v:refname
Guest *Dean Attali* @ 2016-04-08 22:49:49 originally posted:
Really good info. I should start following these rules. Thanks
Guest *Yu Wan* @ 2017-05-26 00:53:04 originally posted:
This is a good idea and I am going to follow it.
Sign in to join the discussion
Sign in with GitHub