{"action":"closed","issue":{"url":"https://api.github.com/repos/nodejs/node/issues/2216","labels_url":"https://api.github.com/repos/nodejs/node/issues/2216/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/node/issues/2216/comments","events_url":"https://api.github.com/repos/nodejs/node/issues/2216/events","html_url":"https://github.com/nodejs/node/issues/2216","id":96380857,"number":2216,"title":"Branding Release Channels","user":{"login":"mikeal","id":579,"avatar_url":"https://avatars.githubusercontent.com/u/579?v=3","gravatar_id":"","url":"https://api.github.com/users/mikeal","html_url":"https://github.com/mikeal","followers_url":"https://api.github.com/users/mikeal/followers","following_url":"https://api.github.com/users/mikeal/following{/other_user}","gists_url":"https://api.github.com/users/mikeal/gists{/gist_id}","starred_url":"https://api.github.com/users/mikeal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikeal/subscriptions","organizations_url":"https://api.github.com/users/mikeal/orgs","repos_url":"https://api.github.com/users/mikeal/repos","events_url":"https://api.github.com/users/mikeal/events{/privacy}","received_events_url":"https://api.github.com/users/mikeal/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/node/labels/meta","name":"meta","color":"fef2c0"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-21T18:13:55Z","updated_at":"2015-10-07T05:22:44Z","closed_at":"2015-10-07T05:22:44Z","body":"We have a number of builds that we want to be consumed by different audiences and we need to find a way to message those channels and a strategy for promoting them to the correct audience.\r\n\r\nThis topic is descendent from the big release process issue: https://github.com/nodejs/io.js/issues/1997\r\n\r\n* Lastest LTS\r\n* Supported LTS\r\n* Maintenance Mode LTS (Is this the right term?)\r\n* Incubating Master (we need to start incubating master releases before promoting for wider consumption)\r\n* Incubated Master (Previously referred to as \"stable\" or \"current\" master, basically the latest master build that passed incubation)\r\n* Latest `next` release.\r\n\r\nObviously we won't feature all of these on the front page and we may have different strategies for promoting them on twitter, that's one of the things we need to figure out along with the branding.\r\n\r\nPinging relevant working groups:\r\n@nodejs/website \r\n@nodejs/evangelism \r\nI'll also make sure the Marketing Committee at the foundation lends their expertise."}}