Ugh…, This argument again. We’ve had this discussion already in this tread:
and before that in this thread:
and a bunch of other times before that in yet more theads that I don’t feel like looking up. This is one of those areas where blender has chosen its own way to go about things. I personally prefer a naming scheme that refers to each release by the year and month it came out on rather than any numbers based names, but either way I don’t think it matters too much in the end.
In your case, I think the best solution is to do as safetyman suggested and download the zip version for each release first.
Edit:No wait, I take that back. Your best option would probably be to copy the contents of the current version before updating, then add a folder named config under its “version” folder (In this case the folder is named “2.79”). This will make the copy of the current version portable, and you will always have that version as a backup in case there are issues with the new version.
They don’t wait until any sort of “major” release to do things like update which version of python blender uses, so addons do at times need to be updated in order to work for an incremental release.