zclllyybb commented on issue #64065:
URL: https://github.com/apache/doris/issues/64065#issuecomment-4610681861
Breakwater-GitHub-Analysis-Slot: slot_7e689c9aedcd
Initial analysis: this issue looks like a release-notes draft/tracking item
for Apache Doris 4.0.6, not a runtime bug report or a request for a code fix.
I checked the live issue metadata. It is open, has no labels, no milestone,
no assignees, and no existing discussion. The body links back to the 4.0.5
release notes, has a clear Behavior Changes section, and covers the main
user-visible areas for 4.0.6: cloud-mode improvements, observability, lineage,
correctness fixes, load/integrity fixes, storage/compaction fixes, lakehouse
fixes, security updates, and stability fixes.
One release-process gap to confirm before publication: I can see public
`4.0.6-rc01` and `4.0.6-rc02` tags, but I did not find a published GitHub
release named `4.0.6` at the time of this check. So the notes should not be
treated as final unless the release manager has already fixed the final
artifact/tag boundary elsewhere.
Suggested maintainer actions:
- Add the same process metadata used by the previous release-notes issue, at
least the `release notes` label, and a milestone if the project uses one for
4.0.x maintenance releases.
- Confirm that every referenced PR is included in the final 4.0.6
release/cherry-pick range, especially the Behavior Changes and
data-loss/correctness fixes.
- Add or link the final release artifact/tag/checksum page once available.
If this is still RC-stage content, make that explicit in the issue or keep the
issue open until the final release is published.
- Double-check the Behavior Changes wording before closing:
`enable_strict_consistency_dml` default change, Time Series Compaction
threshold change, `segments_key_bounds_truncation_threshold`, Cluster Snapshot
root privilege requirement, and JSONB/Variant distribution-column rejection are
the items most likely to affect upgrade planning.
- After the final release is published, close this tracking issue or link it
from the official release announcement so users have a stable destination.
No query logs, BE/FE logs, profiles, or reproduction steps are needed for
this issue unless maintainers want to audit a specific listed fix. The main
missing information is release-process metadata and confirmation that the PR
list matches the final 4.0.6 artifact.
--
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]
