# Tagging releases? Useful or not? **URL:** \ **Category:** Build-Test-Release\ **Created:** [September 16, 2020, 11:39am UTC](https://discuss.openedx.org/t/tagging-releases-useful-or-not/3243 "2020-09-16T11:39:45Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![nedbat](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/nedbat/32/3317_2.png) [@nedbat](https://discuss.openedx.org/u/nedbat)\ **Post date:** [September 30, 2020, 4:33pm UTC](https://discuss.openedx.org/t/tagging-releases-useful-or-not/3243/16 "2020-09-30T16:33:58Z")
> [@sambapete](#): > > Because I do have local modifications in our fork, testing against master (or anything that isn’t a fixed point in time if you prefer) does not give me anything worth testing against until there is a release candidate, tag or whatever you call it. So, I might just skip my testing until there is an open-release/xxx.1 tag. Since we are getting into the details of tagging, keep in mind that funky git syntax can get you a fixed point in time whenever you want: **`open-release/juniper.master@{2020-08-01}`** is Juniper master as it was on August 1st. (Updated: that syntax won’t work in GitHub urls for fetching code during install, so it won’t work for our purposes…) --- _[View the full topic](https://discuss.openedx.org/t/tagging-releases-useful-or-not/3243)._