{"action":"opened","issue":{"url":"https://api.github.com/repos/typelevel/cats/issues/1341","repository_url":"https://api.github.com/repos/typelevel/cats","labels_url":"https://api.github.com/repos/typelevel/cats/issues/1341/labels{/name}","comments_url":"https://api.github.com/repos/typelevel/cats/issues/1341/comments","events_url":"https://api.github.com/repos/typelevel/cats/issues/1341/events","html_url":"https://github.com/typelevel/cats/issues/1341","id":174363742,"number":1341,"title":"Consider freezing cats-kernel","user":{"login":"non","id":218045,"avatar_url":"https://avatars.githubusercontent.com/u/218045?v=3","gravatar_id":"","url":"https://api.github.com/users/non","html_url":"https://github.com/non","followers_url":"https://api.github.com/users/non/followers","following_url":"https://api.github.com/users/non/following{/other_user}","gists_url":"https://api.github.com/users/non/gists{/gist_id}","starred_url":"https://api.github.com/users/non/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/non/subscriptions","organizations_url":"https://api.github.com/users/non/orgs","repos_url":"https://api.github.com/users/non/repos","events_url":"https://api.github.com/users/non/events{/privacy}","received_events_url":"https://api.github.com/users/non/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-31T19:56:44Z","updated_at":"2016-08-31T19:56:44Z","closed_at":null,"body":"Hi folks,\r\n\r\nAs per the comments on this *algebra* PR (https://github.com/non/algebra/pull/162) I want to start thinking about freezing *cats-kernel*. By freezing, I mean turning on MiMA compatibility checking, and committing to keeping the API stable for a relatively long timeframe (e.g. a year or more).\r\n\r\nBefore we do this I want to be be sure that the design of *cats-kernel* and *algebra* works for Spire (and Algebird too). We should also be sure that it works for Cats.\r\n\r\nHas anyone identified problems in the design of *cats-kernel* that would break compatibility to fix? Is there anything people think is essential to add or change? I know the design is slightly inconsistent with Cats (necessarily for compatibility reasons). I'm asking more about the names, methods, and type classes than about these kinds of consistency concerns, but if you feel strongly about those feel free to bring them up here.\r\n\r\nWhat do you all think? From a Cats-centric point of view, is *cats-kernel* ready to be declared done?"}}
{"actor":{"display_login":"non"}}