{"action":"created","issue":{"url":"https://api.github.com/repos/nengo/nengo/issues/694","labels_url":"https://api.github.com/repos/nengo/nengo/issues/694/labels{/name}","comments_url":"https://api.github.com/repos/nengo/nengo/issues/694/comments","events_url":"https://api.github.com/repos/nengo/nengo/issues/694/events","html_url":"https://github.com/nengo/nengo/issues/694","id":66716638,"number":694,"title":"How to reference a non-release version","user":{"login":"jgosmann","id":850157,"avatar_url":"https://avatars.githubusercontent.com/u/850157?v=3","gravatar_id":"","url":"https://api.github.com/users/jgosmann","html_url":"https://github.com/jgosmann","followers_url":"https://api.github.com/users/jgosmann/followers","following_url":"https://api.github.com/users/jgosmann/following{/other_user}","gists_url":"https://api.github.com/users/jgosmann/gists{/gist_id}","starred_url":"https://api.github.com/users/jgosmann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jgosmann/subscriptions","organizations_url":"https://api.github.com/users/jgosmann/orgs","repos_url":"https://api.github.com/users/jgosmann/repos","events_url":"https://api.github.com/users/jgosmann/events{/privacy}","received_events_url":"https://api.github.com/users/jgosmann/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nengo/nengo/labels/discussion","name":"discussion","color":"207de5"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-04-06T22:07:05Z","updated_at":"2015-04-14T20:42:39Z","closed_at":null,"body":"I am in the process of making my n-back model code public. I didn't run this model with an official Nengo release, but the `spaopt-v2` branch, more precisely with revision 8fb4eccb6bf5df6149988d0f251e73645347eb71.\r\n\r\n1. What is the best way to reference this particular revision?\r\n2. How do we ensure that it doesn't disappear (e.g., through history rewrites, rebasing, merging, etc.)?\r\n\r\nProbably assigning a tag to that revision is the best option? Should we use a particular naming scheme?"},"comment":{"url":"https://api.github.com/repos/nengo/nengo/issues/comments/93053483","html_url":"https://github.com/nengo/nengo/issues/694#issuecomment-93053483","issue_url":"https://api.github.com/repos/nengo/nengo/issues/694","id":93053483,"user":{"login":"hunse","id":1952250,"avatar_url":"https://avatars.githubusercontent.com/u/1952250?v=3","gravatar_id":"","url":"https://api.github.com/users/hunse","html_url":"https://github.com/hunse","followers_url":"https://api.github.com/users/hunse/followers","following_url":"https://api.github.com/users/hunse/following{/other_user}","gists_url":"https://api.github.com/users/hunse/gists{/gist_id}","starred_url":"https://api.github.com/users/hunse/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hunse/subscriptions","organizations_url":"https://api.github.com/users/hunse/orgs","repos_url":"https://api.github.com/users/hunse/repos","events_url":"https://api.github.com/users/hunse/events{/privacy}","received_events_url":"https://api.github.com/users/hunse/received_events","type":"User","site_admin":false},"created_at":"2015-04-14T20:42:39Z","updated_at":"2015-04-14T20:42:39Z","body":"So I don't see what's wrong with a tag, then. You're not worried about this from a citing standpoint, right (i.e. it doesn't have to be guaranteed that it is unchanged since the time of publication)? You just want people who read your paper to be able to consistently find the right version of Nengo to run your model, which they should be able to do with a tag. While the tag could still be purposely overwritten, it's pretty much impossible to accidentally overwrite it. So go with a tag.\r\n\r\nI think you can name it whatever you want, but it might help to connect to the name of your ctn-archive repo. The simplest might just be to name it \"gosmann-cogsci2015\"."}}