{"action":"created","issue":{"url":"https://api.github.com/repos/ckeditor/ckeditor5/issues/246","repository_url":"https://api.github.com/repos/ckeditor/ckeditor5","labels_url":"https://api.github.com/repos/ckeditor/ckeditor5/issues/246/labels{/name}","comments_url":"https://api.github.com/repos/ckeditor/ckeditor5/issues/246/comments","events_url":"https://api.github.com/repos/ckeditor/ckeditor5/issues/246/events","html_url":"https://github.com/ckeditor/ckeditor5/issues/246","id":166291998,"number":246,"title":"Dealing with cross-repo changes","user":{"login":"Reinmar","id":156149,"avatar_url":"https://avatars.githubusercontent.com/u/156149?v=3","gravatar_id":"","url":"https://api.github.com/users/Reinmar","html_url":"https://github.com/Reinmar","followers_url":"https://api.github.com/users/Reinmar/followers","following_url":"https://api.github.com/users/Reinmar/following{/other_user}","gists_url":"https://api.github.com/users/Reinmar/gists{/gist_id}","starred_url":"https://api.github.com/users/Reinmar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Reinmar/subscriptions","organizations_url":"https://api.github.com/users/Reinmar/orgs","repos_url":"https://api.github.com/users/Reinmar/repos","events_url":"https://api.github.com/users/Reinmar/events{/privacy}","received_events_url":"https://api.github.com/users/Reinmar/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-07-19T09:54:35Z","updated_at":"2016-07-19T11:02:47Z","closed_at":null,"body":"CKEditor 5 uses [multi-repo architecture](https://medium.com/content-uneditable/why-we-chose-a-multirepo-architecture-for-ckeditor-5-54c7e50af1f5). One of the downsides of this solution is that some changes in one repo may require changes in other repos as well.\r\n\r\nI think that there are two possible ways to organise such changes, in a way which will be... organised :D.\r\n\r\n1. In the repository which triggers some change you create a ticket and a PR for that ticket (branch name `t/xxx`). In other repositories you create only PRs but clearly referencing the original PR (branch names `t/ckeditor5-trigger-repo/xxx`).\r\n\r\n  Now, to mark that some changes were made in all those repositories, you add the original ticket **and** other PRs (so those which don't have their respective tickets) to the current milestone. This way in all repositories in which something's changed, there's some \"issue\" (PRs are kind of issues as well) in the milestone.\r\n\r\n2. We create tickets for every single PR made to any repo. If one ticket triggers changes in 5 other repos, then you create 5 additional tickets.\r\n\r\nThe second solution looks better from the \"history\" perspective. It adds more overhead, but just by checking issues you can learn what has changed. This will be important when releasing suff and, most importantly, for the community when assessing releases. However, the first way may be acceptable as well, because changes are marked within milestones anyway, just not as normal issues:\r\n\r\n(this screenshot shows that a PR and issue was added to a milestone, which isn't the point – I've just wanted to show that PRs are displayed in a milestone)\r\n\r\n![screen shot 2016-07-19 at 11 52 23](https://cloud.githubusercontent.com/assets/156149/16945900/5bce501c-4da7-11e6-814a-52d5dd7ff148.png)\r\n\r\nHowever, it may be confusing why we're milestoning some PRs and some we don't. I'm fine with that, but are you? Or have you got other ideas?\r\n"},"comment":{"url":"https://api.github.com/repos/ckeditor/ckeditor5/issues/comments/233599545","html_url":"https://github.com/ckeditor/ckeditor5/issues/246#issuecomment-233599545","issue_url":"https://api.github.com/repos/ckeditor/ckeditor5/issues/246","id":233599545,"user":{"login":"maxbarnas","id":1112966,"avatar_url":"https://avatars.githubusercontent.com/u/1112966?v=3","gravatar_id":"","url":"https://api.github.com/users/maxbarnas","html_url":"https://github.com/maxbarnas","followers_url":"https://api.github.com/users/maxbarnas/followers","following_url":"https://api.github.com/users/maxbarnas/following{/other_user}","gists_url":"https://api.github.com/users/maxbarnas/gists{/gist_id}","starred_url":"https://api.github.com/users/maxbarnas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maxbarnas/subscriptions","organizations_url":"https://api.github.com/users/maxbarnas/orgs","repos_url":"https://api.github.com/users/maxbarnas/repos","events_url":"https://api.github.com/users/maxbarnas/events{/privacy}","received_events_url":"https://api.github.com/users/maxbarnas/received_events","type":"User","site_admin":false},"created_at":"2016-07-19T11:02:47Z","updated_at":"2016-07-19T11:02:47Z","body":"I am for second solution. Referencing other issues, at least in _main_ issue, would be nice too."}}
{"actor":{"display_login":"maxbarnas"}}