Copyright: update manually or automatically by update_tag()?

[muzimuzhi]

When checking whether latest l3build version 2023-12-13-2 (which added back shebang to l3build.lua hence will re-enable CI) is obtained by TeX Live, I find the copyright in l3build.lua doesn't cover 2023, which seems wrong since l3build.lua has been updated several times in 2023.

l3build/l3build.lua

Line 5 in 1cae1aa

File l3build.lua Copyright (C) 2014-2022 The LaTeX Project

Some of the l3build-*.lua files have similar problem.

Local tests show that the code to update copyright used by latex3 repository in build-config.lua works for l3build repository too.

Questions:

• Is it ok to add 2023 to copyright notices to all l3build*.lua files even if some of them are not updated in 2023?
• Does l3build want to keep precise copyright year lists, like
  

  l3build/l3build-help.lua

  Line 3 in 1cae1aa

  File l3build-help.lua Copyright (C) 2018,2020,2021 The LaTeX Project

[josephwright]

I think @FrankMittelbach would say go for just a range and cover all the files equally

[FrankMittelbach]

Some people view copyright dates as dates indicating in which something has changed, but technically we have the copyight even in year in which we don't do changes. The distinction is only important if the changes are made by different parties and you want to highlight that all changes in one year are done by person X while in another year changes by Y and Z have been made, etc , ie you establish individual copyrights. But given that we don't do that here and it is anyway only a formality, I'm indeed for just giving a range (tas long as is reasonable, ie not make a file that is only 1 year old say that it is copyrighted for a whole decade)