@Rocky Any reason to skip branch-4.0.15? just see only branch-4.0.14 and branch-4.0.16

In the StarRocks release cycle, it is common for specific patch versions (like 4.0.15) to be skipped if a critical issue or blocker is discovered during the final stages of the release process. While there is no public post-mortem specifically detailing why 4.0.15 was bypassed, here is the context based on current release patterns: * Release Timing: As of September 2026, v4.0.14 was the stable release (around early September). The appearance of branch-4.0.16 suggests that the 4.0.16 patch is the current target or the most recent stable release. * Version Skipping: When a build for a specific version (e.g., 15) fails internal testing or contains a regression discovered at the last minute, the release team often bumps the version number to the next one (e.g., 16) to ensure a clean release without any confusion from potential "leaked" or broken 4.0.15 artifacts. * Recommendation: There is no reason to seek out 4.0.15. Patch releases are cumulative, so v4.0.16 includes all the bug fixes intended for 4.0.15, plus the additional fixes that likely necessitated the skip. If you are looking for specific bug fixes, you can check the StarRocks GitHub Releases or the official Release Notes (which will jump directly from 4.0.14 to 4.0.16 if 15 was officially skipped). References • release_notes/release-4.0.md