Den tors 31 mars 2022 kl 02:21 skrev Nathan Hartman <
hartman.nat...@gmail.com>:

> On Wed, Mar 30, 2022 at 4:10 PM <hartmannat...@apache.org> wrote:
>
>> Author: hartmannathan
>> Date: Wed Mar 30 20:10:06 2022
>> New Revision: 1899394
>>
>> URL: http://svn.apache.org/viewvc?rev=1899394&view=rev
>> Log:
>> * branches/1.14.x/STATUS: Nominate r1896609 (bump copyright year to 2022)
>>
>> Modified:
>>     subversion/branches/1.14.x/STATUS
>>
>> Modified: subversion/branches/1.14.x/STATUS
>> URL:
>> http://svn.apache.org/viewvc/subversion/branches/1.14.x/STATUS?rev=1899394&r1=1899393&r2=1899394&view=diff
>>
>> ==============================================================================
>> --- subversion/branches/1.14.x/STATUS (original)
>> +++ subversion/branches/1.14.x/STATUS Wed Mar 30 20:10:06 2022
>> @@ -46,6 +46,13 @@ Candidate changes:
>>     votes:
>>       +1: markphip
>>
>> + * r1896609
>> +   Bumps copyright date to 2022
>> +   Justification:
>> +     Show correct year in output.
>> +   Votes:
>> +     +1: hartmannathan
>> +
>>  Veto-blocked changes:
>>  =====================
>
>
>
> We should try to get the above backport nomination approved, both for
> 1.10.8 and 1.14.2, because it would look rather silly to release with last
> year's copyright date.
>
> I am in the process of digging through numerous changes on trunk to see if
> there are additional ones appropriate for backport that were missed.
>
> The others that I have nominated so far are, like the above, very low risk.
>
> I'm trying to pick beneficial ones that I believe won't instigate any
> last-minute complications like test failures etc.
>

Thanks for doing this! I've voted for them and while not explicitly
mentioned as exceptions in the voting process, I believe it doesn't count
as core code and thus I've also approved them.

They should be part of tomorrow's backport batch. I will be on the road
from early Friday morning (CET) until Sunday afternoon, but I'll try to
keep an eye on the backports to make sure everything goes smooth.

/Daniel

Reply via email to