[sr-dev] Tagging versions

[Olle E. Johansson]

19 dec 2012 kl. 20:41 skrev Victor Seva <linuxmaniac at torreviejawireless.org>:

> I really don't see any task apart of doing a "git tag v3.3.3" "git
> push origin v3.3.3" in the moment of the realease.
> 
> Am I missing something? Do you want me to do such work?

At least one of the people asking for this stated as a reason "to be able to follow bug fixes".

We do bug fixes in the 3.3 branch in git - unless we change policy, create a 3.3.3 branch and
start cherry picking between them all. 

So far a release never changes - a 3.3.3 tag will never change, it's the same as the .tar.gz,
it is frozen. If you want to get bug fixes for 3.3.3, then check out the 3.3 branch from git
and follow that.

This doesn't mean that tagging is useless, it serves a purpose but not the one 
asked for.

/O