[= ;256869]
If you find yourself developing on a version which you find stable and suitable to your needs, then it is definitely wise to remain on that version of the engine. becomes even more true as you near the end of your project. However if you wish to test out a later version, remember that you should always be doing so by making a copy of your project and updating that copy. way, in case there are any issues, you still have your original project on the older version.
[/]
A big problem is not that the project changes when updating to a new version - if you’re using Source Control it’s easy to role back - but that if an update has an, you have to go back to the previous full release. I couldn’t, for example, go from 4.7.3 to 4.7.2 via the Launcher. can be even more problematic with Preview versions, which can be more unstable.
Would it be possible, for example, to update the Launcher so that it’s possible to get any of the updates the currently released version, and list all preview builds to get whilst the current version is in a preview state?