On Sun, 3 Mar 2019 at 12:20, Vladimir Sitnikov <[email protected]> wrote: > > sebb> otherwise why make a release? > > For instance to validate that sha1 of the produced jars would match > (cross-check for MITM)
That's not a release, but I get the point that the build would create a different file if done in a different year. > If we take the year from notice it might be a bit odd, but it would confine > the year to a single place. Alternatively, the copyright year could be defined in the build file, and used to populate the files that need it. It's important that the year is correct in the releases that we make. I think it is currently (except possibly for the edge case of an early January release), but if you want to change the process, feel free, so long as releases have the correct year. Other builds are not releases. > Vladimir
