licenses: updating licenses#69904
Conversation
|
This change is |
jlinder
left a comment
There was a problem hiding this comment.
Looking at http://unlicense.org, the license can be slightly modified to not include the last line ("For more information, please refer to https://unlicense.org"). If all the dependencies that use this license do not remove that line, then including just one file for it seems right.
Reviewed 6 of 6 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status:complete! 0 of 0 LGTMs obtained (waiting on @bdarnell)
bdarnell
left a comment
There was a problem hiding this comment.
The presence of two BSL licenses is unfortunate. Let's rename the boost one to Boost-BSL.txt. (alternately, we could follow the SPDX convention and use BSL for boost and BUSL for business. But we refer to BSL.txt all over the place and I'm not eager to make that change right now).
updating BSL license for release branch 21.2 Release justification: Non-production code change Release note: None
Release justification: Non-production code change Release note: None
e382c32 to
a1939b0
Compare
celiala
left a comment
There was a problem hiding this comment.
TFTRs!
I'll plan to merge this as soon as tests pass. Afterwards, I'll also backport this to release-21.2, as approved in triage meeting.
Looking at http://unlicense.org, the license can be slightly modified to not include the last line ("For more information, please refer to https://unlicense.org"). If all the dependencies that use this license do not remove that line, then including just one file for it seems right.
Ack, done.
The presence of two BSL licenses is unfortunate. Let's rename the boost one to Boost-BSL.txt. (alternately, we could follow the SPDX convention and use BSL for boost and BUSL for business. But we refer to BSL.txt all over the place and I'm not eager to make that change right now).
Ack, done.
Reviewable status:
|
bors r+ |
|
Build succeeded: |
As part of Creating a release branch for release-21.2, this PR:
This PR is one of the tasks detailed in #70751, which tracks all the steps relevant to creating a release branch for
${vBRANCH_CUT}and preparing master for the${vNEXT}major version.Release justification: Non-production code change
Release note: None