At Thu, 18 Jul 2013 09:11:28 +0200, Togan Muftuoglu wrote: > When I check the current HEAD tag of the master this is what I get. Is > this what it should be if not can it be fixed so it reflects reality? > > ~/devel/git-sources/racket $ git describe --tags HEAD > v5.0.1-12863-g3c0b799
I think this result reflects that we don't generally tag commits in the master branch. We tag releases, but those are normally commits (that were constructed via branches) that are not reachable from HEAD. It happens that v5.0.1 coincides with a commit reachable form HEAD (for reasons I don't know or remember), and so that've why you get a "v5.0.1" release. Maybe it would be good to add a tag (more recent than "v5.0.1") that doesn't include a version number, so it's not so misleading? Or is it worth adjusting our release process to introduce a tag that indicates when a release version branched from master? _________________________ Racket Developers list: http://lists.racket-lang.org/dev
