{"action":"created","issue":{"url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1600","labels_url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1600/labels{/name}","comments_url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1600/comments","events_url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1600/events","html_url":"https://github.com/HaxeFlixel/flixel/issues/1600","id":104476236,"number":1600,"title":"Haxelib release of 4.0.0","user":{"login":"Tiago-Ling","id":1617118,"avatar_url":"https://avatars.githubusercontent.com/u/1617118?v=3","gravatar_id":"","url":"https://api.github.com/users/Tiago-Ling","html_url":"https://github.com/Tiago-Ling","followers_url":"https://api.github.com/users/Tiago-Ling/followers","following_url":"https://api.github.com/users/Tiago-Ling/following{/other_user}","gists_url":"https://api.github.com/users/Tiago-Ling/gists{/gist_id}","starred_url":"https://api.github.com/users/Tiago-Ling/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Tiago-Ling/subscriptions","organizations_url":"https://api.github.com/users/Tiago-Ling/orgs","repos_url":"https://api.github.com/users/Tiago-Ling/repos","events_url":"https://api.github.com/users/Tiago-Ling/events{/privacy}","received_events_url":"https://api.github.com/users/Tiago-Ling/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-09-02T13:07:27Z","updated_at":"2015-09-02T13:37:25Z","closed_at":null,"body":"Hey guys, with the recent closure on #1471 by @larsiusprime i think it's a good time to schedule a definitive date for releasing a stable version to haxelib.\r\n\r\nComparing the latest release on haxelib (3.3.11) to what we have now on dev, i think it's much better and even stable than before. \r\n\r\nThere may be some issues left to solve, and it would be great if we could list them here. Ideally these issues would be only bugs, and only \"game-breaking\" ones.\r\n\r\nAn idea would be to take advantage of @Beeblerox 's presence here to solve the worst problems and then make the release in ~2 weeks. \r\n\r\nWhat do you think?\r\n\r\n<bountysource-plugin>\r\n---\r\nWant to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26388584-haxelib-release-of-4-0-0?utm_campaign=plugin&utm_content=tracker%2F254189&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F254189&utm_medium=issues&utm_source=github).\r\n</bountysource-plugin>"},"comment":{"url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/comments/137083719","html_url":"https://github.com/HaxeFlixel/flixel/issues/1600#issuecomment-137083719","issue_url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1600","id":137083719,"user":{"login":"larsiusprime","id":739064,"avatar_url":"https://avatars.githubusercontent.com/u/739064?v=3","gravatar_id":"","url":"https://api.github.com/users/larsiusprime","html_url":"https://github.com/larsiusprime","followers_url":"https://api.github.com/users/larsiusprime/followers","following_url":"https://api.github.com/users/larsiusprime/following{/other_user}","gists_url":"https://api.github.com/users/larsiusprime/gists{/gist_id}","starred_url":"https://api.github.com/users/larsiusprime/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/larsiusprime/subscriptions","organizations_url":"https://api.github.com/users/larsiusprime/orgs","repos_url":"https://api.github.com/users/larsiusprime/repos","events_url":"https://api.github.com/users/larsiusprime/events{/privacy}","received_events_url":"https://api.github.com/users/larsiusprime/received_events","type":"User","site_admin":false},"created_at":"2015-09-02T13:37:25Z","updated_at":"2015-09-02T13:37:25Z","body":"These are both good comments. I think rather than committing to a date we just need to commit to the **idea** that a release is actually really happening. Move it from the mental space of \"some day...\" to \"reasonably soon.\"\r\n\r\nStart making some issues and plans towards that goal, figure out everything that needs to be done to make it happen, start working through it, and then only commit to a date once we have a very good feel for how fast we're progressing.\r\n\r\nAnd I agree that committing to a 100% painless upgrade is impossible. This is a breaking change release, and as far as I can tell, it's by design -- we kind of intentionally put as many breaking changes in as we could so that we wouldn't be dropping them one by one in subsequent releases.\r\n\r\nSo our responsibility is to provide as much documentation and help as we are reasonably able, but not over-promise that people won't have to refactor their code.\r\n\r\nI think a big part of easing the transition is just some useful advice in a FAQ. Like:\r\n\r\nQ: Should I upgrade to Flixel 4.0.0?\r\nA: Not necessarily! If you have all the features you need, just finish your current game in Flixel 3.x, and wait until your next one to move to Flixel 4.0.0.\r\n\r\nEtc."}}