 Hit me up if you get stuck on anything. I did that during last release. (re @kc2bez: For some of the qt things making sure the symbols are updated is a bit tricky too.)
[14:11] <apt-ghetto> RikMills: Do you have a minute?
[14:11] <RikMills> hi
[14:12] <apt-ghetto> When I package a new upstream release, I see in the debian/copyright file an entry like "Files: *" and "Copyright: 2012-2019 LXQt team"
[14:13] <apt-ghetto> Should I update the year to 2021 for the LXQt team?
 I think that is referring to the Debian team.
[14:14] <RikMills> if the files in question have had changes made by that team, then yes you could
[14:14] <apt-ghetto> In the source files, there is often something like "Copyright: 2013 - LXQt team" but they do not update the copyright info
[14:17] <RikMills> is this the lxqt lxqt team or the debian lxqt team?
[14:17] <apt-ghetto> In my understanding it is the upstream LXQt team: https://github.com/lxqt/liblxqt/blame/0.17.0/lxqtglobals.h
[14:17] <apt-ghetto> And  the Debian LXQt team could or should have the copyright only for debian/* Files
[14:19] <RikMills> ok, the upstream qxt team have no changed that file recently, so I would leave the year as it is
[14:20] <RikMills> use the dates in the file, not the git history
[14:21] <RikMills> a packager is not expected to scan the upstream git repo for dates of all source files
[14:22] <RikMills> you have to just go with the dats on the file in the source tar to keep things sane and manageable
[14:23] <apt-ghetto> Ok, thanks. Do you use a helper script for the copyright things?
[14:24] <RikMills> I often use decopy, sometimes licensecheck
[14:24] <apt-ghetto> Thanks, I will have a look at it.
 Thanks RikMills
[14:25] <RikMills> saying that, last few things I did that had the newer SPDX type copyright headers, just grep'ing the source tree for those worked best