Tags

[m4rcs]

Hi,

could you please make a Tag for each Release of your great Plugin, so I can submit it to cdnjs.

See here.

[max-favilli]

More than willing, but what does it mean "make a Tag"?

Max Favilli
[email protected]
mobile (+39) 348 3367064
type http://maxfavilli.com in your webbrowser
"Be conservative in what you do, be liberal in what you accept from
others." (Jon Postel)

On Thu, Jun 20, 2013 at 4:19 PM, m4rcs [email protected] wrote:

Hi,

could you please make a Tag for each Release of your great Plugin, so I
can submit it to cdnjs https://github.com/cdnjs/cdnjs.

See here cdnjs/cdnjs#1354.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/176
.

[m4rcs]

Take a look at the git manual: http://git-scm.com/book/en/Git-Basics-Tagging

[cowwoc]

Please take the 30 seconds needed to resolve this issue. All you need to do is checkout the right revision and run git tag <name>. For example, git tag v1.7

[Skysplit]

@asual
+1 for this
I think It would be really nice to have tag, as it'll help to use this library properly as bower dependency instead of depending on master branch (which could be unstable)

{
    "dependencies": {
        "jquery-address": "master"
    } 
}

vs

{
    "dependencies": {
        "jquery-address": "~1.6"
    } 
}

[glensc]

i'm also looking for this!

but authors should not modify existing releases, once v1.6 is tagged, next version should be v1.6.1, not re-tag same version again.

i've created tags in my repo, owners with push permission to this repo can pull in the tags:

git clone https://github.com/asual/jquery-address.git
cd jquery-address
git remote add glen https://github.com/glensc/jquery-address.git
git fetch glen
git push origin --tags -n
git push origin --tags

-n will show what tags would be pushed, if all looks ok, run without it. but you can push out also individual tags:

git push origin v1.3

tagged for now:

• v1.0 - - unable to find matching commit in git for this zip
• v1.1 2b59e2e
• v1.2 c9cf5c2
• v1.2.1 52765e6
• v1.2.2 5ca432e
• v1.3 5aa2dd4
• v1.3.1 b505e9a - this is not exact content as zip, but preceeding and next commit are very different already
• v1.3.2 bc1cae6
• v1.4 7d51e2c
• v1.5 33d0c5d
• v1.6 - not created, as can not find any zip for this release to check which commit matches

i think v1.6 should be not tagged at all if exact commit can be found, and next version v1.7 (or 1.6.1) be created instead.