{"action":"created","issue":{"url":"https://api.github.com/repos/SuperDARN/rst/issues/54","repository_url":"https://api.github.com/repos/SuperDARN/rst","labels_url":"https://api.github.com/repos/SuperDARN/rst/issues/54/labels{/name}","comments_url":"https://api.github.com/repos/SuperDARN/rst/issues/54/comments","events_url":"https://api.github.com/repos/SuperDARN/rst/issues/54/events","html_url":"https://github.com/SuperDARN/rst/pull/54","id":224612418,"number":54,"title":"Release 4.0","user":{"login":"ksterne","id":3009489,"avatar_url":"https://avatars1.githubusercontent.com/u/3009489?v=3","gravatar_id":"","url":"https://api.github.com/users/ksterne","html_url":"https://github.com/ksterne","followers_url":"https://api.github.com/users/ksterne/followers","following_url":"https://api.github.com/users/ksterne/following{/other_user}","gists_url":"https://api.github.com/users/ksterne/gists{/gist_id}","starred_url":"https://api.github.com/users/ksterne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ksterne/subscriptions","organizations_url":"https://api.github.com/users/ksterne/orgs","repos_url":"https://api.github.com/users/ksterne/repos","events_url":"https://api.github.com/users/ksterne/events{/privacy}","received_events_url":"https://api.github.com/users/ksterne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2017-04-26T22:01:06Z","updated_at":"2017-04-30T14:29:16Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/SuperDARN/rst/pulls/54","html_url":"https://github.com/SuperDARN/rst/pull/54","diff_url":"https://github.com/SuperDARN/rst/pull/54.diff","patch_url":"https://github.com/SuperDARN/rst/pull/54.patch"},"body":"This pull request starts the new release testing period.  We can use this to check out what merge conflicts we've got here and resolve them.  The plan for now is to merge this pull request sometime on May 31st."},"comment":{"url":"https://api.github.com/repos/SuperDARN/rst/issues/comments/298235423","html_url":"https://github.com/SuperDARN/rst/pull/54#issuecomment-298235423","issue_url":"https://api.github.com/repos/SuperDARN/rst/issues/54","id":298235423,"user":{"login":"sshepherd","id":2982719,"avatar_url":"https://avatars0.githubusercontent.com/u/2982719?v=3","gravatar_id":"","url":"https://api.github.com/users/sshepherd","html_url":"https://github.com/sshepherd","followers_url":"https://api.github.com/users/sshepherd/followers","following_url":"https://api.github.com/users/sshepherd/following{/other_user}","gists_url":"https://api.github.com/users/sshepherd/gists{/gist_id}","starred_url":"https://api.github.com/users/sshepherd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sshepherd/subscriptions","organizations_url":"https://api.github.com/users/sshepherd/orgs","repos_url":"https://api.github.com/users/sshepherd/repos","events_url":"https://api.github.com/users/sshepherd/events{/privacy}","received_events_url":"https://api.github.com/users/sshepherd/received_events","type":"User","site_admin":false},"created_at":"2017-04-30T14:29:16Z","updated_at":"2017-04-30T14:29:16Z","body":"The issue of version numbers and git has been discussed at length during\nworkshops in the past. It was decided that while git is good for versioning\nof the development software, we need a separate versioning mechanism for\nthe release software.\n\nOn Sun, Apr 30, 2017 at 12:00 AM, Kevin Sterne <notifications@github.com>\nwrote:\n\n> @pasha-ponomarenko <https://github.com/pasha-ponomarenko>, minor version\n> numbers still are a bit odd to talk about in the git world, but I get they\n> make sense when talking about pre-git development. I'm hoping more so that\n> we can get away from at least minor version numbers in the future. Git\n> itself is version control, so I don't think we need another layer on top of\n> it. But that's probably another discussion that doesn't necessarily apply\n> here.\n>\n> Thanks for clarifying the two tracks that the master and develop branch\n> took with respect to the fitacf.2.5 library. In an ideal world, I'd love to\n> figure out where the develop refactored code starts breaking on the\n> twofreq data. But I'm probably one of the only ones that might want to see\n> that happen and I'm betting I won't have the time between now and the\n> release date to figure this out. From the sounds of it, I think you'd\n> rather just keep the code for the fitacf.2.5 library as it is in the\n> master branch. Is that right? I don't think this requires an additional\n> pull request, but more so just resolving the merge conflicts.\n>\n> I think if we go this route though, then the refactoring that was done in\n> the develop branch will be \"lost\" or at least not easily accessed again.\n> Is this something we're OK with? I'm guessing so if we're already looking\n> towards a redo of fitacf with \"v3\".\n>\n> Also, @egthomas <https://github.com/egthomas>, @kkotyk\n> <https://github.com/kkotyk>, long live nano!\n>\n> —\n> You are receiving this because you were mentioned.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/SuperDARN/rst/pull/54#issuecomment-298209677>, or mute\n> the thread\n> <https://github.com/notifications/unsubscribe-auth/AC2DPzk8RemZgydjQrBr71fhFWKxF8Qiks5r1AdVgaJpZM4NJevF>\n> .\n>\n"}}
{"actor":{"display_login":"sshepherd"}}