I just finished my game a few days ago with 3.17 im wondering what is other peoples opinions should I click the release button or does any one recommend I do the extra work to updating my game to 3.17.1 ?
1 Like
It should just be a drop in replacement to 3.17
However, if you are ready to release just release. You can upgrade the engine to 3.17.1 for your 1.1 release. :-).
1 Like
ok thanks for the feedback 
, ps what does “drop in replacement” mean ?
I mean that you should just be able to switch to 3.17.1 from 3.17.
1 Like
meaning I could just create a new project with 3.17.1 and transfer over my .h and .cpp files correct ?
Yup. Or maybe even drop in the new cocos2d folder.
1 Like
The solution is good, but I thought this could use a “I second that” comment.
Never upgrade any dependency (lib/engine) that works if your release is within a month or two.
(you could upgrade it in a develop/feature branch, but not master/trunk)
There have been unforeseen issues that occur in a high percentage of engine upgrade attempts that I’ve seen or worked on.
3 Likes
so I should wait then to update to 3.17.1?
It would be wise…if your game is ready to go. deploy it. let people play it. get feedback, etc. the longer you wait, perhaps you never deploy it because of scope creep?
Then upgrade to 3.17.1 later when you need/want to.
1 Like