[Release] Add 4.0.0 release guide and rearrange community docs - #823
Merged
Conversation
mag1c1an1
force-pushed
the
release_plan
branch
2 times, most recently
from
August 12, 2026 05:54
625d792 to
5a86877
Compare
Signed-off-by: mag1cian <mag1cian@icloud.com>
Signed-off-by: mag1cian <mag1cian@icloud.com>
Co-Authored-By: Codex <noreply@openai.com> Signed-off-by: mag1cian <mag1cian@icloud.com>
Signed-off-by: mag1cian <mag1cian@icloud.com>
mag1c1an1
force-pushed
the
release_plan
branch
from
August 13, 2026 08:24
5a86877 to
72a6ad3
Compare
xuchen-plus
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces the LakeSoul 4.0.0 Release Guide and reorganizes the repository's community documentation into
docs/community/.Motivation
LakeSoul is moving toward a layered release model (Core / Python / connectors) starting with
4.0.0. This document definesthe target versioning strategy, release artifacts, supported platforms, and the release process so that subsequent RC and
final-tag cuts can follow a consistent, auditable flow.
Subsequent PRs will incrementally implement the version-sync scripts, multi-arch native packaging, and GitHub Actions release
gates described here. Until that work lands, the existing
deployment.ymlmust not be used to publish4.0.0directly.Changes
docs/release/release-4.0.0.md— the 4.0.0 release guide (versioning strategy, domains, artifacts, supportedplatforms, full release workflow, rollback policy).
docs/release/release-guide.md— the release prcess start at 4.0.0.guideline.md,guideline-cn.md,roles-cn.md, andcommunity-roles.mdintodocs/community/and update links inREADME.md/README-CN.md/CONTRIBUTING.md.Commits
add release docrelease: add release doc / rearrange docsAll commits are signed off.
Contribution guidelines followed: branch
release_plan, PR title prefixed with[Release]. These are docs-only changes,so no code tests are applicable.