LCORE-1649: LTS process overview by tisnik · Pull Request #1950 · lightspeed-core/lightspeed-stack

tisnik · 2026-06-19T07:03:16Z

Description

LCORE-1649: LTS process overview

Type of change

Tools used to create PR

Assisted-by: N/A
Generated by: N/A

Related Tickets & Documents

Related Issue #LCORE-1649

Summary by CodeRabbit

Documentation

Added new "Container Orchestration Guide" documentation link
Added comprehensive "Long-Term Support (LTS) Process Overview" guide with detailed runbook, including process steps, roles, responsibilities, branching strategies, CI/CD requirements, and rollback procedures
Updated documentation index with new guide links

coderabbitai · 2026-06-19T07:03:29Z

Warning

Review limit reached

@tisnik, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 41 minutes and 52 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4472a012-6a5f-4fcd-8778-67e6d6a78790

📥 Commits

Reviewing files that changed from the base of the PR and between aac3131 and bf9f18d.

📒 Files selected for processing (3)

docs/README.md
docs/index.md
docs/lts_flow.md

Walkthrough

Adds a new docs/lts_flow.md document covering the end-to-end LTS process, runbooks, branching strategy, CI/CD gates, rollback procedures, communication templates, and an embedded SVG flow diagram. Two navigation entries are added to docs/README.md and one to docs/index.md linking to this new page.

Changes

LTS Documentation

Layer / File(s)	Summary
Navigation links in docs index files `docs/README.md`, `docs/index.md`	Inserts a "Container Orchestration Guide" link under "Installation and configuration" in `README.md`, and an "LTS provess overview" link under "Releasing" in both `README.md` and `index.md`.
New LTS process and runbook document `docs/lts_flow.md`	Adds 753 lines covering the LTS process overview (goals, roles, modular components, decision policies, branching/versioning, CI/CD gates, rollback/emergency procedures, communication templates, observability, automation), an embedded printable SVG flow diagram alongside copied prompt/response transcript lines, and a full "LTS Process & Runbook" section with concise runbooks, example workflow, implementation checklist, and glossary/FAQ.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

lightspeed-core/lightspeed-stack#1738: Updates the same docs/README.md and docs/index.md navigation by adding "Releasing" documentation links, directly adjacent to where the LTS overview link is inserted.
lightspeed-core/lightspeed-stack#1845: Modifies the same docs navigation entries in docs/README.md and docs/index.md to add the "Container Orchestration Guide" link also inserted by this PR.
lightspeed-core/lightspeed-stack#1928: Updates the "Releasing" navigation section in docs/README.md and docs/index.md by adding a release-process related link, the same location where the LTS overview link is added here.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly aligns with the primary change: adding LTS process overview documentation. It references the issue ticket (LCORE-1649) and clearly identifies the main focus as the LTS process overview, which is reflected across all modified files (README.md, index.md, and the new lts_flow.md).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

✨ Simplify code

Create PR with simplified code

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/lts_flow.md`:
- Around line 240-249: Remove all internal conversation transcript fragments
from the documentation file to ensure only polished final content is published.
Specifically, delete all lines containing the meta-narrative markers such as
"User prompt", "GPT-5 mini:", and separator lines (----) that appear before and
after the SVG code block. The SVG diagram itself starting with the XML
declaration should remain intact. Search through the file and remove these
conversation context lines while preserving the actual technical content and
diagrams that follow them.
- Line 1: The markdown document violates linting rules MD022 (blank lines around
headings) and MD001 (heading hierarchy). Add a blank line immediately before
each heading in the document to comply with MD022, and change the first heading
from ### to ## to ensure proper heading level increment from top-level to
sub-level (fixing MD001). Apply these corrections to all headings mentioned: the
first heading at line 45 and all subsequent headings at lines 51, 63, 73, 141,
147, 161, 168, 176, 182, 187, 193, 200, 209, 221, 418 and any others throughout
the document that follow the same pattern.

In `@docs/README.md`:
- Line 86: The link text contains a spelling error where "provess" should be
"process". In the navigation link "LTS provess overview", correct the misspelled
word "provess" to "process" so it reads "LTS process overview". This same typo
correction needs to be applied in both docs/README.md and docs/index.md files to
ensure consistency across documentation.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0abb2f82-ec73-4ca0-a618-f9153464bb27

📥 Commits

Reviewing files that changed from the base of the PR and between 1f7d8ac and aac3131.

📒 Files selected for processing (3)

docs/README.md
docs/index.md
docs/lts_flow.md

📜 Review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)

GitHub Check: build-pr
GitHub Check: integration_tests (3.13)
GitHub Check: E2E: server mode / ci / group 3
GitHub Check: E2E: library mode / ci / group 2
GitHub Check: E2E: server mode / ci / group 2
GitHub Check: E2E: library mode / ci / group 1
GitHub Check: E2E: library mode / ci / group 3
GitHub Check: E2E Tests for Lightspeed Evaluation job
GitHub Check: E2E: server mode / ci / group 1
GitHub Check: Konflux kflux-prd-rh02 / lightspeed-stack-on-pull-request
GitHub Check: Konflux kflux-prd-rh02 / lightspeed-stack-0-6-on-pull-request

🧰 Additional context used

🪛 LanguageTool

docs/index.md

[grammar] ~93-~93: Ensure spelling is correct
Context: .../lightspeed-stack/releasing.html) [LTS provess overview](https://lightspeed-core.githu...