Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

[RFC] Keeping v1.x branch in sync with master branch w.r.t. license and legal changes #19920

Open
mseth10 opened this issue Feb 19, 2021 · 1 comment
Labels
RFC Post requesting for comments

Comments

@mseth10
Copy link
Contributor

mseth10 commented Feb 19, 2021

Problem statement

In the past few months, several PRs related to license and legal changes have been merged to master branch. Not all of these changes were back-ported to v1.x branch. There is an effort required to keep v1.x branch updated with these changes and in sync with the master branch.

Proposed solutions

Towards this effort, I scanned through some license related files (LICENSE, NOTICE, rat-excludes, license/* and tools/license_header.py) and made sure that they are up-to-date with changes in master branch. In doing so, I identified the following PRs in master branch made in past 3 months:

with corresponding PRs in v1.x branch (created ones that were missing):

With these PRs, all the above mentioned files are updated in v1.x branch and are in sync with master branch.

Creating this RFC to get inputs from community on what other license related files to look into and if there is any other license related PRs that is missed here. Thanks!

@mseth10 mseth10 added the RFC Post requesting for comments label Feb 19, 2021
@sandeep-krishnamurthy
Copy link
Contributor

Thank you Manu for helping with these that will enable apache compliant releases of 1.X.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
RFC Post requesting for comments
Projects
None yet
Development

No branches or pull requests

2 participants