A quick reminder for developers: now that we're in a new year, if you update your copyright to manually be "2019" there's almost certainly a spot for you in hell. Don't kick this down the road--solve the problem forever with something like DateTime.UtcNow.Year (or whatever your language of choice does for current year).

I just approved a ticket that changes 2016-2018 to 2016-{DateTime.UtcNow.Year} because there were three separate pull requests in the past that didn't address this. Now, barring any systemic changes to how .NET calculates the current UTC DateTime, we will never have to update this again.

July 12, 2016

February 16, 2017

July 13, 2018

January 17, 2019