Improve release doc and script

[kezhenxu94]

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
• Update the CHANGES log.

[Copilot]

Pull Request Overview

This PR updates the release documentation to improve the process of creating release artifacts and starting the next release iteration.

• Header changes to clarify the artifact creation process.
• Replaces detailed manual steps with streamlined commands that download and execute release scripts.
• Removes outdated manual instructions for building and tagging releases.

Files not reviewed (3)

• docs/en/changes/changes.tpl: Language not supported
• tools/releasing/create_release_tars.sh: Language not supported
• tools/releasing/start_next_version.sh: Language not supported

Comments suppressed due to low confidence (2)

docs/en/guides/How-to-release.md:19

• Consider adding a verification step (e.g., checksum validation) for the downloaded script to mitigate potential security risks from remote script execution.

curl -Ls https://raw.githubusercontent.com/apache/skywalking/refs/heads/master/tools/releasing/create_release_tars.sh | bash -

docs/en/guides/How-to-release.md:38

• It is unclear what this script does compared to the previous manual instructions. Please add a brief explanation or a link to documentation outlining the changes performed by this script.

curl -Ls https://raw.githubusercontent.com/apache/skywalking/refs/heads/master/tools/releasing/start_next_version.sh | bash -

[wu-sheng]

Cool. It is great to have release scripts more automatically.

[wu-sheng]

@kezhenxu94 Kafka case fails due to the reason I sent to you yesterday night. And we only got temp fix through locking version.

[kezhenxu94]

@kezhenxu94 Kafka case fails due to the reason I sent to you yesterday night. And we only got temp fix through locking version.

Locking version is not a temp fix in my opinion, it’s always a good practice to lock versions of dependencies to not break CI all of a sudden

[wu-sheng]

@kezhenxu94 Kafka case fails due to the reason I sent to you yesterday night. And we only got temp fix through locking version.

Locking version is not a temp fix in my opinion, it’s always a good practice to lock versions of dependencies to not break CI all of a sudden

Yes. That is true. My intention was, the version lock is for a previous version, not for the latest.

[wu-sheng]

About #13144, I am waiting for hot/warm/cold doc update, then we could merge that.