{"action":"created","issue":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/800","repository_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort","labels_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/800/labels{/name}","comments_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/800/comments","events_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/800/events","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/800","id":185020410,"number":800,"title":"Version Control","user":{"login":"jsmallcombe","id":15150313,"avatar_url":"https://avatars.githubusercontent.com/u/15150313?v=3","gravatar_id":"","url":"https://api.github.com/users/jsmallcombe","html_url":"https://github.com/jsmallcombe","followers_url":"https://api.github.com/users/jsmallcombe/followers","following_url":"https://api.github.com/users/jsmallcombe/following{/other_user}","gists_url":"https://api.github.com/users/jsmallcombe/gists{/gist_id}","starred_url":"https://api.github.com/users/jsmallcombe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsmallcombe/subscriptions","organizations_url":"https://api.github.com/users/jsmallcombe/orgs","repos_url":"https://api.github.com/users/jsmallcombe/repos","events_url":"https://api.github.com/users/jsmallcombe/events{/privacy}","received_events_url":"https://api.github.com/users/jsmallcombe/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-10-25T05:12:36Z","updated_at":"2016-10-25T23:10:30Z","closed_at":null,"body":"Apologies if this has been brought up before/recently/elsewhere, but I haven't seen it.\r\n\r\nBranches for developing new features are all well and good but I've notice an almost continual modification of the master as more and more development is done and the guts of GRSISort are ripped out and put back in multiple times, sometimes transparently, sometimes not, will little in the way of delineation.\r\n\r\nThis may be fine for those working together every day on the bleeding edging pushing GRIFFIN computing, but its not so good for all situations.\r\n\r\nWhat I'm pushing for is more use of the tag system and version numbers, and specifically establishing 2 clear landmarks:\r\n1 - The collaborations current \"stable\" version i.e. not on the bleeding edge, a little out of date, but something coop students etc only here for a few months or more external collaborators not involved in GRSISort development can be given to use without having to worry about hidden monsters.\r\n2 - Clear version number changes to indicate when fragment/analysis trees become incompatible\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/comments/256205520","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/800#issuecomment-256205520","issue_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/800","id":256205520,"user":{"login":"jsmallcombe","id":15150313,"avatar_url":"https://avatars.githubusercontent.com/u/15150313?v=3","gravatar_id":"","url":"https://api.github.com/users/jsmallcombe","html_url":"https://github.com/jsmallcombe","followers_url":"https://api.github.com/users/jsmallcombe/followers","following_url":"https://api.github.com/users/jsmallcombe/following{/other_user}","gists_url":"https://api.github.com/users/jsmallcombe/gists{/gist_id}","starred_url":"https://api.github.com/users/jsmallcombe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsmallcombe/subscriptions","organizations_url":"https://api.github.com/users/jsmallcombe/orgs","repos_url":"https://api.github.com/users/jsmallcombe/repos","events_url":"https://api.github.com/users/jsmallcombe/events{/privacy}","received_events_url":"https://api.github.com/users/jsmallcombe/received_events","type":"User","site_admin":false},"created_at":"2016-10-25T23:10:30Z","updated_at":"2016-10-25T23:10:30Z","body":"The idea would be to only iterate the \"stable version\" infrequently once major bugs are quelled but before any large changes, merging of new feature branches etc.\r\nYou are right Ryan people do just go straight for the master, we can perhaps curb this behaviour by establishing a system and pointing people to it, say on the front page of the wiki.\r\nWe certainly appreciate all your hard work Ryan. Is there actually a changelog in the wiki I'm not seeing or do you just mean you try and keep the wiki up to date?\r\n\r\nI suggest a 4 part tag for EVERY commit\r\n-Major system changes, branch merge\r\n-Changes breaking fragment trees\r\n-Changes breaking analysis trees\r\n-Commit iterator\r\ne.g. 3.1.2.15\r\n\r\nAnd I guess we update what is the \"stable version\" a little after the fact. "}}
{"actor":{"display_login":"jsmallcombe"}}