{"action":"created","issue":{"url":"https://api.github.com/repos/esp8266/Arduino/issues/904","labels_url":"https://api.github.com/repos/esp8266/Arduino/issues/904/labels{/name}","comments_url":"https://api.github.com/repos/esp8266/Arduino/issues/904/comments","events_url":"https://api.github.com/repos/esp8266/Arduino/issues/904/events","html_url":"https://github.com/esp8266/Arduino/issues/904","id":112038082,"number":904,"title":"Remove IDE code from the repository","user":{"login":"igrr","id":4349050,"avatar_url":"https://avatars.githubusercontent.com/u/4349050?v=3","gravatar_id":"","url":"https://api.github.com/users/igrr","html_url":"https://github.com/igrr","followers_url":"https://api.github.com/users/igrr/followers","following_url":"https://api.github.com/users/igrr/following{/other_user}","gists_url":"https://api.github.com/users/igrr/gists{/gist_id}","starred_url":"https://api.github.com/users/igrr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/igrr/subscriptions","organizations_url":"https://api.github.com/users/igrr/orgs","repos_url":"https://api.github.com/users/igrr/repos","events_url":"https://api.github.com/users/igrr/events{/privacy}","received_events_url":"https://api.github.com/users/igrr/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/esp8266/Arduino/labels/core","name":"core","color":"fad8c7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2015-10-18T20:05:31Z","updated_at":"2015-10-30T07:32:34Z","closed_at":null,"body":"This ticket should track long due repository overhaul. Since the Boards manager was introduced, it doesn't make sense to maintain the whole IDE fork in this repository. We only need the files under hardware/esp8266com/esp8266, plus some scripts to build/bundle/upload boards manager package.\r\nESP8266FS tool should go into a separate repository.\r\n\r\nThis cleanup will allow us to remove tags inherited from the IDE (e.g. 1.6.5) and start maintaining a sane version numbering scheme for the core alone (currently versions look like `1.6.5-1160-gef26c5f` which is a shame).\r\n\r\nThere are three ways to do the cleanup.\r\n\r\n1. Remove IDE files, move core files to new locations, and commit everything. Pros: easy to do, commit history is mostly preserved (`git log --follow`), rebasing of pending pull requests is straightforward. Cons: this will generate a huge diff, and repository download will get much larger.\r\n\r\n2. Move core files to new locations and purge all commits inherited from the IDE, along with corresponding files. Pros: commit history for the esp8266 core preserved (same as with option 1), we get clean history and repository size is reduced considerably. Cons: this will mess up history, so any pending changes from pull requests will need to be applied manually. Also if some contributor is working on a large piece of code he will be rather disappointed by not being able to merge.\r\n\r\n3. Rename repository into esp8266/old-Arduino, create new repository called esp8266/Arduino with all the core files. Pros: clean repo, small download size, history may be preserved (same as with option 2). Cons: github doesn't allow to transfer issues from one repository to another, so issues will be lost (and isn't that lovely? :) )\r\n\r\nPersonally I'm inclined to go with option 2. However this may upset people who are currently working on some pieces of code. So I'm leaving this ticket open until next week to gather comments, perhaps there is another better option which I'm missing here.\r\n"},"comment":{"url":"https://api.github.com/repos/esp8266/Arduino/issues/comments/152449900","html_url":"https://github.com/esp8266/Arduino/issues/904#issuecomment-152449900","issue_url":"https://api.github.com/repos/esp8266/Arduino/issues/904","id":152449900,"user":{"login":"pgollor","id":9283623,"avatar_url":"https://avatars.githubusercontent.com/u/9283623?v=3","gravatar_id":"","url":"https://api.github.com/users/pgollor","html_url":"https://github.com/pgollor","followers_url":"https://api.github.com/users/pgollor/followers","following_url":"https://api.github.com/users/pgollor/following{/other_user}","gists_url":"https://api.github.com/users/pgollor/gists{/gist_id}","starred_url":"https://api.github.com/users/pgollor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pgollor/subscriptions","organizations_url":"https://api.github.com/users/pgollor/orgs","repos_url":"https://api.github.com/users/pgollor/repos","events_url":"https://api.github.com/users/pgollor/events{/privacy}","received_events_url":"https://api.github.com/users/pgollor/received_events","type":"User","site_admin":false},"created_at":"2015-10-30T07:32:34Z","updated_at":"2015-10-30T07:32:34Z","body":"@igrr At first: Great work :-).\r\nWith which tool do you generate the stable and staging releases?\r\nIt is better to modify your scripts instead of creating a new one, isn't it?\r\n\r\nWhat we are need?\r\n* bash script to compressing the current git code as zip and this to a tag or release?\r\n* Python script to modify the json template file which adds the current tools version and so on\r\n\r\nIf we have fully automatic scripts we can use a CI system to generate a nightly build board manager package or so :)\r\n\r\nI hope you are understanding my thoughts. ;-)\r\nIf you are want, I can try to create the two scripts from above."}}