{"action":"created","issue":{"url":"https://api.github.com/repos/sipwise/rtpengine/issues/154","labels_url":"https://api.github.com/repos/sipwise/rtpengine/issues/154/labels{/name}","comments_url":"https://api.github.com/repos/sipwise/rtpengine/issues/154/comments","events_url":"https://api.github.com/repos/sipwise/rtpengine/issues/154/events","html_url":"https://github.com/sipwise/rtpengine/issues/154","id":105666782,"number":154,"title":"Any chance we can get a new tag?","user":{"login":"etamme","id":21685,"avatar_url":"https://avatars.githubusercontent.com/u/21685?v=3","gravatar_id":"","url":"https://api.github.com/users/etamme","html_url":"https://github.com/etamme","followers_url":"https://api.github.com/users/etamme/followers","following_url":"https://api.github.com/users/etamme/following{/other_user}","gists_url":"https://api.github.com/users/etamme/gists{/gist_id}","starred_url":"https://api.github.com/users/etamme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/etamme/subscriptions","organizations_url":"https://api.github.com/users/etamme/orgs","repos_url":"https://api.github.com/users/etamme/repos","events_url":"https://api.github.com/users/etamme/events{/privacy}","received_events_url":"https://api.github.com/users/etamme/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-09-09T19:20:54Z","updated_at":"2015-09-11T08:33:35Z","closed_at":null,"body":"A few fixes have gone in upstream recently to allow for building on older versions of both kernels, and centos.  Is there any way we can get a new tag at commit c6ff5e7c03fa49ef6216d7cfe09b3006ddb5d5f8 or later so we have some upstream marker vs. creating a local tag or branch off the commit?\r\n"},"comment":{"url":"https://api.github.com/repos/sipwise/rtpengine/issues/comments/139485387","html_url":"https://github.com/sipwise/rtpengine/issues/154#issuecomment-139485387","issue_url":"https://api.github.com/repos/sipwise/rtpengine/issues/154","id":139485387,"user":{"login":"taurus-forever","id":1928266,"avatar_url":"https://avatars.githubusercontent.com/u/1928266?v=3","gravatar_id":"","url":"https://api.github.com/users/taurus-forever","html_url":"https://github.com/taurus-forever","followers_url":"https://api.github.com/users/taurus-forever/followers","following_url":"https://api.github.com/users/taurus-forever/following{/other_user}","gists_url":"https://api.github.com/users/taurus-forever/gists{/gist_id}","starred_url":"https://api.github.com/users/taurus-forever/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/taurus-forever/subscriptions","organizations_url":"https://api.github.com/users/taurus-forever/orgs","repos_url":"https://api.github.com/users/taurus-forever/repos","events_url":"https://api.github.com/users/taurus-forever/events{/privacy}","received_events_url":"https://api.github.com/users/taurus-forever/received_events","type":"User","site_admin":false},"created_at":"2015-09-11T08:33:35Z","updated_at":"2015-09-11T08:33:35Z","body":"The commit c6ff5e7 is in master only for the moment (which is upcoming mr4.1.1.1).\r\nTo tag c6ff5e7 as mr4.0.1.3 we have to rollback changes to NGCP release mr4.0 build 1 (branched mr4.0 and mr4.0.1) which are a bit different code base. \r\n\r\nOur general policy is to spend our resources on high quality fast releases instead of on backporting.\r\nSo, for the moment you can tag your fork internally somehow and switch back to upstream as soon as mr4.1.1.1 is publicly available. I see no problems with that approach for you."}}