Am 22.07.2013 11:21, schrieb Jeroen De Dauw:
Hey,
I did not suggest using any existing deployment branches for this purpose. If we
use the tags for demotime, we can just have a demotime branch.
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...
GitHub thinks it has 36 releases, and packagist things
the latest release is
2013-06-something.
Github and Packagist equate tags with releases? Huh. I'd say that sucks in a
roayl way - to me, tags on master serve a completely different purpose. Only
tags on a lelease branch mark actual releases.
If this interpretation is a general convention, then I agree with your concerns,
because then our tagging policy is misleading. But using branches instead of
"internal tags" seems bad too. How do other projects handle this?
-- daniel