According to the official git docu "Like most VCSs, Git has the ability to tag specific points in history as being important. Generally, people use this functionality to mark release points (v1.0, and so on)."

So, yeah, it would allow for Daniel's interpretation, which I indeed share. But looking at actual usage, my completely unrepresentative survey confirms that they are used for marking releases and releace-candidates mostly. I couldn't find a single instance where they use it for, well, tagging a specific version for anything else.

It seems that a number of widespread tools are also assuming this usage. I would have suggested to take this to the weekly meeting to discuss, but since we already spend sufficiently time here on the topic I would suggest to
* switch to tags for releases
* think about our release strategy
* use either a branch for demo or just take the commit-hash

OK?

Cheers,
Denny





2013/7/22 Daniel Kinzler <daniel.kinzler@wikimedia.de>
>     That would work, but seems nonsensical to me: tags are immutable, branches are
>     mutable. We want to makr a specific version, using an immutable marker is the
>     correct tool.
>
>     At least in theory...
>
> And this leads to problems how?

As long as nobody messes with the branch, it doesn't. Just like using a variable
instead of a constant doesn't cause problems... until it does.

-- daniel


_______________________________________________
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech



--
Project director Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. +49-30-219 158 26-0 | http://wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.