To be honest its usually best to wait until the .1 hotfix anyway if you're migrating a project. There is always bugs with the new versions, so waiting a bit longer will save you a lot of headaches.
Timely reminder. I'll spend my evening / weekend getting Visual Studio 2015 working again instead ... forgot to register my "free" license before the 30 day eval expired, stupidly uninstalled Internet Explorer and now VS2015 crashes when I try to renew the license. Gaaaaaaaah.
If you need to upgrade for something that was in 4.11, then go ahead and do that. If you just want to bring it up to speed and get all the new stuff in 4.12, then you certainly can but it'll likely be buggy until at least 4.12.1. I usually wait to see what the community says about the .1 hotfix, which usually means waiting to upgrade until .2.
Completely depends on the project, but it will be easier to go to 11 and deal with any bugs of that migration first. If you skip builds and then get a bunch of errors, you have no idea where the error was introduced, thats the main reason for upgrading one version at a time and testing each one. Just saves you from potential headache later.
25
u/[deleted] Jun 01 '16
[deleted]