add year 2023 to Notice files

[yangjf2019]

No description provided.

[nikita15p]

Looks good to me. Cc @busbey @rgoers can u please approve

[busbey]

you also need to update the year in flume-ng-clients/flume-ng-log4jappender/src/main/resources-for-jar-with-deps/META-INF/NOTICE

Can someone confirm that project.build.outputTimestamp in flume-parent/pom actually gets updated to 2023 for e.g. the generated NOTICE file in jars and the dist archive? Even if it does, do we want to change it to 2023 so that SNAPSHOT builds have a correct year?

[yangjf2019]

flume-ng-clients/flume-ng-log4jappender/src/main/resources-for-jar-with-deps/META-INF/NOTICE

Thanks for your review.I updated.

[rgoers]

The proper way to change this is to change the copyright line from

Copyright 2011-2022 The Apache Software Foundation

to

Copyright 2011-Present The Apache Software Foundation

From a legal perspective, copyright notices aren't required to be present in the files. If they are they should contain the year of creation and may contain years in which substantial modifications were made. But replacing the ending year with "present" eliminates the need to ever change them again.

[rgoers]

Change "2023" to "Present"

[rgoers]

Same here

[busbey]

I'm -0 on switching to use "Present". At least my reading of the published ASF policy on NOTICE files requires actual years.

text like "present" is ambiguous because it requires that the consumer of the NOTICE file have additional context about when that file was created / modified / distributed.

[yangjf2019]

@busbey Done, thanks!