If it helps, I've already tested the upgrade from 2.0.15 up to 2.0.17 (and prior to that, 2.0.14 to 2.0.15) on 2 separate SMF instances and have yet to encounter any issues. One instance was fairly vanilla, the other had quite a bit more tweaking. That is to say, using the standard SMF upgrade procedure, all goes smoothly. If you tend to shy away from the automated approach in favor of a more hands-on method, obviously YMMV.
If the repository you are running the site on right now matches what is in your github, I'd be happy to throw the code base onto my testdev server and see if it handles the upgrade smoothly. Mind you, it would be with my own database (obviously, I know, but it's worth stating in case that adds additional points of anxiety when it comes to doing the upgrade on your production env).