apache/pinot

Automate License and Notice Binary update manual step

Open

#15,460 建立於 2025年4月3日

在 GitHub 查看
 (4 留言) (0 反應) (1 負責人)Java (4,937 star) (1,234 fork)batch import
good first issuehelp wantedstale

描述

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.

貢獻者指南

技術棧
javashell
領域
releaseci cd
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Understanding of Apache Pinot release processKnowledge of Gradle or Maven build scriptsFamiliarity with shell scriptingFamiliarity with LICENSE/NOTICE files in Apache projects
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
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.
Automate License and Notice Binary update manual step · apache/pinot#15460 | Good First Issue