@Rocky why this pr github.com/StarRocks/starrocks/pull/67099 didn't backport to any branch?

I couldn't find the specific title or details for Pull Request #67099 in the current documentation or public release notes. However, based on the PR numbers surrounding it (like #67098 and #67100, which appeared in the StarRocks 4.0 release cycle around early 2026), here are the most common reasons why a PR is not backported to stable branches: * PR Classification: StarRocks follows a strict backporting policy based on the PR type. While

[BugFix]

PRs are almost always backported to active stable branches,

[Feature]

and

[Refactor]

PRs are typically only merged into the

main

branch for the next major/minor release (e.g., 4.1 or 5.0). If #67099 was an internal refactor or a new feature, it would intentionally stay in

main

. * Version State: Stable branches (like

branch-4.0

) move through states:

open

->

feature-freeze

->

bugfix-only

->

code-freeze

. Once a branch reaches

bugfix-only

, only critical fixes are backported. Since #67099 is missing from the 4.0.x patch notes where its neighbors appear, it likely did not meet the criteria for a stable branch backport at that time. * Merge Conflicts: Automated backporting (triggered by labels like

cherry-pick-x.x

) can fail if there are significant code differences between

main

and the target branch. If a conflict occurs, the backport requires a manual PR; if no one performs this manual step, the change remains only in

main

. * PR Status: If the PR was closed without being merged, or if it was superseded by another PR (like a combined fix), it wouldn't be backported. If this PR contains a fix or feature you specifically need in a stable version, the best course of action is to comment on the PR or reach out in the StarRocks Slack to request a manual cherry-pick. References • administration/management/monitoring/metrics.md • sql-reference/data-types/other-data-types/HLL.md • administration/management/proc_profile.md • knowledge/usage/best-practice.md • sql-reference/sql-functions/date-time-functions/now.md • administration/management/BE_configuration.md • administration/http_interface/query_detail.md