projectured: update source.txt to use tagged-git instead of branched-git

[attila-lendvai]

No description provided.

[quicklisp]

Why?

[attila-lendvai]

tags provide more freedom to move them around. if the history of branches are overwritten, then it can cause headaches when people pull on them.

[quicklisp]

So the "quicklisp" tag may move around?

[attila-lendvai]

yes, that's the plan. because there'll be a major reorg that will rewrite the history of the master branch, and rename master to something historical. when a new stable state is reached, then moving the tag feels more natural than rewriting the quicklisp branch.

but i can be easily convinced why not to do this if there are any reasons.

[quicklisp]

If I have a repo checked out with a tag, what do I need to do to follow a tag that has moved?

[attila-lendvai]

to push:

$ git push -f origin taggg
Counting objects: 1, done.
Writing objects: 100% (1/1), 163 bytes | 0 bytes/s, done.
Total 1 (delta 0), reused 0 (delta 0)
To /tmp/origin
 + f54c750...7e88e2e taggg -> taggg (forced update)

to pull:

$ git tag -ln
taggg           tag test banan
$ git pull --tags
remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
From /tmp/origin
 - [tag update]      taggg      -> taggg
Already up-to-date.
$ git tag -ln
taggg           asdfffff tag desc

[attila-lendvai]

note: fetch --tags also works the same as pull. i've created a PR for the ql-controller repo to add it.

[fiddlerwoaroof]

Maybe it'd be better to expect a tag of the format quicklisp-<id> where the lexically greatest is pulled as the current version? That way, you don't have to move tags around and can keep track of all the released commits.

[attila-lendvai]

that'd be unnecessary complexity, i think.

tags in version control systems are labels to denote a specific revision. and that's exactly what we need here: a symbolic constant that quicklisp can refer to, and that the project authors can move around freely to whichever revision they deem appropriate for the next quicklisp release.

and if git tags happen to give some headaches, then they need to be addressed/kludged (i don't think that is the case).

[attila-lendvai]

FTR, this is that PR in ql-controller: quicklisp/quicklisp-controller#11

[ryukinix]

I think using git tag based releases is a good thing.