Tagging releases? Useful or not?

[nedbat (Ned Batchelder)]

@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…)