+
Skip to content

improve DR-002 executive summary #1799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 26, 2025
Merged

improve DR-002 executive summary #1799

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1f8c25d
improve DR-002 executive summary
AlexanderLanin Sep 24, 2025
51c0a6b
add typical workflow section
AlexanderLanin Sep 24, 2025
6fb2424
Apply Copilot wording
AlexanderLanin Sep 24, 2025
89a9c3a
Apply Copilot wording
AlexanderLanin Sep 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions docs/design_decisions/DR-002-infra.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,17 +27,28 @@ The concept described here turns a collection of separate repositories into a sy
### Proposed Approach
- Every change in any repository is tested **in combination with the rest of the system**, not just in isolation.
- There are **two testing layers**:
- a **fast feedback loop** (lightweight tests that run on every pull request),
- and a **deeper validation** (heavier tests run after merges or on a schedule).
- a **fast feedback loop** (lightweight tests that run on every pull request BEFORE merge in any repository),
- and a **deeper validation** (heavier tests run after merges or on a schedule BEFORE release in any repository).
- This setup guarantees that developers can trust the system as a whole to consistently work.

### Typical workflow

* Component PRs are created.
* Run component local verification.
* Run integration testing (quick).
* Post merge:
* Run integration test (full).
* Only after successful integration testing (full) can a release be created.

### Benefits
- Problems across repositories are caught early.
- Developers spend less time coordinating merges (“merge after me” scenarios disappear).
- The project always has a “known good” baseline to fall back on, enabling stability while still moving fast.

Note: this concept is easily extendable to support multiple versions of S-CORE. But that's currently not required.

See Martin Fowler's [continuous integration](https://martinfowler.com/articles/continuousIntegration.html) article for a deeper dive into the topic.

---
## Introduction

Expand Down
点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载