yihua opened a new pull request, #13883: URL: https://github.com/apache/hudi/pull/13883
### Problem Statement After deprecating JIRA for issue tracking, the existing PR template and compliance validation were still designed around the old JIRA-centric workflow. This created friction for contributors who needed to adapt to new prefixes and validation rules that were no longer aligned with the project's current processes. ### Change Logs This change updates the PR template and compliance validation: PR Template Updates: - Adds new "Problem Statement" section as the first required section - Updates placeholder text from underscore-wrapped format (`_text_`) to HTML comments (`<!-- text -->`) so it does not show spurious template content - Removes JIRA ticket requirement from documentation update section PR Compliance Enhancements: - Adds support for new prefixes: `(feat)`, `(fix)`, `(docs)`, `(style)`, `(refactor)`, `(perf)`, `(test)`, `(chore)`, `(improvement)`, `(blocker)`, `(security)` - Implements support for breaking change combinations: `(feat)(breaking)` and `(refactor)(breaking)` - Adds GitHub issue link validation requirement for fix PRs (`(fix)` prefix) - Updates validation to start with Problem Statement section - Enhances test coverage - Maintains backward compatibility with existing `[HUDI-XXXX]` and `[MINOR]` prefixes ### Impact Streamline PR process and compliance checks ### Risk Level none ### Documentation Update To update https://hudi.apache.org/contribute/how-to-contribute ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Change Logs and Impact were stated clearly - [ ] Adequate tests were added if applicable - [ ] CI passed -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
