20 dec 2012 kl. 08:51 skrev Victor Seva <[email protected]>:
> Hi Olle, > > 2012/12/20 Olle E. Johansson <[email protected]>: >> >> 19 dec 2012 kl. 20:41 skrev Victor Seva <[email protected]>: >> >>> 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. > > But the issue is just that. It's easier to know the precise commit of > the release, the asked tag v3.3.3. > That's what I'm talking about. > >> 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. > > If I want now to know how many changes are from the release I have to > check all the logs and guess. > >> This doesn't mean that tagging is useless, it serves a purpose but not the >> one >> asked for. > > Maybe I was not clear enough. Now it's all clear then! /O :-) _______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
