> "© 2010-2023" In the bit of Big Blue that I worked in this is what we did. You only updated the later year if you made a non-insignificant change to a file.

> "© 2010-2023" In the bit of Big Blue that I worked in this is what we did. You only updated the later year if you made a non-insignificant change to a file. Fixing a simple typo in a comment wasn’t enough, nor was just reformatting/moving code. Fixing a bug, changing a user visible string, refactoring, adding a new feature, etc and you’d bump the “to” year. I think there was also some kind of magic rule that you could put the next year (e.g. 2023) from some point late in the current year, something like you could add 2023 if it was November 2022 or later. Don’t think I ever saw these “rules” formally written down so everything was just a kind of folklore passed on from one generation of devs to the next. Copyright years in version/help output was definitely updated as part of the build/release process.