zhengruifeng commented on PR #57818: URL: https://github.com/apache/spark/pull/57818#issuecomment-5211051781
I checked the latest 1,000 commits on `upstream/master` (2026-06-10 through 2026-08-06) to see how the tag is used in practice. - 70 follow-up PR commits were found, plus one revert whose quoted subject contains the tag. - All 70 use `[FOLLOWUP]`; none use `[FOLLOW-UP]`. - 68/70 have an earlier commit carrying the same JIRA ID. - The median gap from the preceding same-JIRA commit is 7 days; 59/68 are within 30 days. Classifying each PR by its primary purpose (some categories overlap at the edges): | Primary use case | Count | | --- | ---: | | Tests, CI, lint, and test coverage | 22 | | Correctness, compatibility, or edge-case fixes | 16 | | Review refinements, refactors, cleanup, or performance | 15 | | Documentation, messages, and version metadata | 7 | | Build, release, packaging, and tooling follow-through | 7 | | Continued implementation or missing support | 3 | Representative examples include correctness fixes (#57820, #57760), post-merge tests or review feedback (#57392, #57631), design refinement (#56606, #56595), documentation or metadata corrections (#57252, #57121), build/release follow-through (#57738, #56996), and missing-mode support (#57024). The common pattern is therefore broader than directly fixing code: `[FOLLOWUP]` describes a PR relationship to specific earlier work. Normal uses include fixes, omitted tests/docs/tooling, post-merge feedback, design refinements, and missing support. JIRA reuse is strongly conventional but not absolute in this sample. Two follow-ups have no earlier commit with the same JIRA: #57738 uses SPARK-58534 for the 4.4 MiMa follow-through, and #57039 uses SPARK-57961 for a linter failure introduced by #57037 (SPARK-57959). This commit-history scan does not by itself establish the release-state boundary; determining whether every preceding change was unreleased would require mapping the earlier PRs to release branches/tags. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
