Tags?

[rxaviers]

It's so exciting to see you follow semver versioning, and you keep packages.json and npm registry updated accordingly. But, it's really hard to checkout code on a certain version since you don't tag it. Tagging also allows users to use another package management tools, eg. bower, to fetch your project.

It would be very positive if you keep your repo tagged according to your semver versioning.

This can be done really easily. You may already know that, but steps are basically:

• commit your updated packages.json;
• git tag <version>
• git push --tags

I can't PR the tags for you. But, basically, the current ones are:

c966cd4: "0.3.4"
aa35786: "0.3.3"
19aa9f1: "0.3.2"
819db32: "0.3.1"
aa5b2ec: "0.3.0"
f88149e: "0.2.4"
b59559c: "0.2.3"
e952a6d: "0.2.2"
378dcb6: "0.2.1"
901b852: "0.2.0"
5690f58: "0.1.4"
104949a: "0.1.3"
b03daea: "0.1.2"
50a245c: "0.1.1"
98e97e9: "0.1.0"

You could achieve tagging them all with

git checkout c966cd4 && git tag "0.3.4"
git checkout aa35786 && git tag "0.3.3"
git checkout 19aa9f1 && git tag "0.3.2"
git checkout 819db32 && git tag "0.3.1"
git checkout aa5b2ec && git tag "0.3.0"
git checkout f88149e && git tag "0.2.4"
git checkout b59559c && git tag "0.2.3"
git checkout e952a6d && git tag "0.2.2"
git checkout 378dcb6 && git tag "0.2.1"
git checkout 901b852 && git tag "0.2.0"
git checkout 5690f58 && git tag "0.1.4"
git checkout 104949a && git tag "0.1.3"
git checkout b03daea && git tag "0.1.2"
git checkout 50a245c && git tag "0.1.1"
git checkout 98e97e9 && git tag "0.1.0"
git push --tags

[rxaviers]

Is anyone live in here?

[fxa]

Thank you for your advice!

I will do the change this weekend – I was very busy this week

Von: Rafael Xavier de Souza [mailto:notifications@github.com]
Gesendet: Freitag, 20. September 2013 20:09
An: fxa/uritemplate-js
Betreff: Re: [uritemplate-js] Tags? (#14)

Is anyone live in here?

—
Reply to this email directly or view it on GitHub #14 (comment) . https://github.com/notifications/beacon/z007K-oJ-ZnzAnsfdzRoGZEZ3lUzP01XoNGNRsfj7dq8Xs2cd57lhygepYu7jG7O.gif

[fxa]

Hello Rafael

Done!

Thanks for detailed explanation.

Von: Rafael Xavier de Souza [mailto:notifications@github.com]
Gesendet: Donnerstag, 19. September 2013 17:02
An: fxa/uritemplate-js
Betreff: [uritemplate-js] Tags? (#14)

It's so exciting to see you follow semver versioning, and you keep packages.json and npm registry updated accordingly. But, it's really hard to checkout code on a certain version since you don't tag it. Tagging also allows users to use another package management tools, eg. bower, to fetch your project.

It would be so positive if you keep your repo tagged according to your semver versioning.

This can be done with really easily. You may already know that, but steps are basically:

• commit your updated packages.json;
• git tag
• git push --tags

I can't PR the tags for you. But, basically, the current ones are:

c966cd4 c966cd4: "0.3.4"
aa35786 aa35786: "0.3.3"
19aa9f1 19aa9f1: "0.3.2"
819db32 819db32: "0.3.1"
aa5b2ec aa5b2ec: "0.3.0"
f88149e f88149e: "0.2.4"
b59559c b59559c: "0.2.3"
e952a6d e952a6d: "0.2.2"
378dcb6 378dcb6: "0.2.1"
901b852 901b852: "0.2.0"
5690f58: "0.1.4"
104949a: "0.1.3"
b03daea: "0.1.2"
50a245c: "0.1.1"
98e97e9: "0.1.0"

You could achieve tagging them all with

git checkout c966cd4 && git tag "0.3.4"
git checkout aa35786 && git tag "0.3.3"
git checkout 19aa9f1 && git tag "0.3.2"
git checkout 819db32 && git tag "0.3.1"
git checkout aa5b2ec && git tag "0.3.0"
git checkout f88149e && git tag "0.2.4"
git checkout b59559c && git tag "0.2.3"
git checkout e952a6d && git tag "0.2.2"
git checkout 378dcb6 && git tag "0.2.1"
git checkout 901b852 && git tag "0.2.0"
git checkout 5690f58 && git tag "0.1.4"
git checkout 104949a && git tag "0.1.3"
git checkout b03daea && git tag "0.1.2"
git checkout 50a245c && git tag "0.1.1"
git checkout 98e97e9 && git tag "0.1.0"
git push --tags

—
Reply to this email directly or view it on GitHub #14 . https://github.com/notifications/beacon/z007K-oJ-ZnzAnsfdzRoGZEZ3lUzP01XoNGNRsfj7dq8Xs2cd57lhygepYu7jG7O.gif

[rxaviers]

\o/ glad to hear, thanks for the prompt action.