4 comments (4 comments)0 reactions (0 reactions)1 assignee (1 assignee)Java1,234 forks (1,234 forks)batch import
good first issuehelp wantedstale
Repository metrics
- Stars
- 4,937 stars (4,937 stars)
- PR merge metrics
- Avg merge 6d 7h (Avg merge 6d 7h)186 merged PRs in 30d (186 merged PRs in 30d)
Description
Depndabot generally raises the PR to upgrade the dependency if a new version is available. This results in the License-binary and Notice-binary files not being updated. For the release process, we need to update these two files, and we are currently following a semi-manual process to do it. Refer here
This issue will try to automate the step.
Contributor guide
- Research direction
- Investigate the current manual process documented at the provided wiki link https://cwiki.apache.org/confluence/display/PINOT/Creating+an+Apache+Release#CreatinganApacheRelease UpdatingLICENSE binaryfile. Examine the existing CI/CD pipeline in the repository (e.g., GitHub Actions workflows) to identify where automation can be integrated. Consider writing a script (e.g., using Gradle or shell) that compares versions of dependencies and updates the LICENSE binary and NOTICE binary files accordingly. Also review any existing maintainer comments in the issue for specific requirements.
- Tech stack
- javashell
- Domain
- releaseci cd
- Issue type
- Feature
- Prerequisites
- Understanding of Apache Pinot release processKnowledge of Gradle or Maven build scriptsFamiliarity with shell scriptingFamiliarity with LICENSE/NOTICE files in Apache projects