On 06/18/2013 12:09 AM, Pádraig Brady wrote: > I notice on some projects like nova and quantum (I presume with milestone > proposed commits) > that the 2013.2.b1 tag was created on the now removed milestone-proposed > branch. > Therefore `git describe` and `git log --decorate` etc. on master, ignore the > latest tag. > I was wondering if it would be better to tag on master itself? > Also could these tags be retroactively be adjusted to point to corresponding > master commits?
Well, we release from the tag, so we can't move them. We've discussed merging milestone-proposed back in to master after release - but there's a few logistical issues about doing that. Perhaps we should revisit that discussion. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
