There are couple of tag types to decide which one to use and then I thought that past releases should be tagged as well if the tags are important to community. Practically is about spotting the commit to Makefile.defs that sets the version -- the commit message should present that very clear.

Cheers,
Daniel

On 12/19/12 8:41 PM, Victor Seva wrote:
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?

2012/12/19 Daniel-Constantin Mierla <[email protected]>:
Hello,

I have nothing against if there is any developer that want to undertake this
task, eventually some more that could make the releases better.

Cheers,
Daniel


On 12/19/12 8:44 AM, Victor Seva wrote:
Hi,

can, please, someone create the tag for the v3.3.3 so It would be
easier to track patches between releases.

Thanks in advance and keep the good work.

_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda


_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Reply via email to