Skip to content
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

docs: update LOTUS_RELEASE_FLOW.MD document #12322

Merged
merged 9 commits into from
Aug 12, 2024
Merged

docs: update LOTUS_RELEASE_FLOW.MD document #12322

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
4a37fa7
Preliminary update to the LOTUS_RELEASE_FLOW document
rjan90 Jul 30, 2024
ba44b6b
docs: update LOTUS_RELEASE_FLOW with recent FAQs and branch/tag strat…
BigLep Aug 9, 2024
673922b
Apply @biglep suggestions from code review
BigLep Aug 9, 2024
e4d3ec7
Apply remaining @biglep suggestions from code review
BigLep Aug 9, 2024
74061af
Added terminology section
BigLep Aug 9, 2024
2175cee
More editing
BigLep Aug 10, 2024
d350be7
Update LOTUS_RELEASE_FLOW.md
rjan90 Aug 12, 2024
8272937
fix: double spacing and minor typos
rjan90 Aug 12, 2024
d26b54f
fix(docs): link to LOTUS_RELEASE_FLOW.md from CONTRIBUTING.md
rjan90 Aug 12, 2024
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
1 change: 1 addition & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ Lotus is a universally open project and welcomes contributions of all kinds: cod
1. If the proposal entails a protocol change, please first submit a [Filecoin Improvement Proposal](https://github.com/filecoin-project/FIPs).
2. If the change is complex and requires prior discussion, [open an issue](github.com/filecoin-project/lotus/issues) or a [discussion](https://github.com/filecoin-project/lotus/discussions) to request feedback before you start working on a pull request. This is to avoid disappointment and sunk costs, in case the change is not actually needed or accepted.
3. Please refrain from submitting PRs to adapt existing code to subjective preferences. The changeset should contain functional or technical improvements/enhancements, bug fixes, new features, or some other clear material contribution. Simple stylistic changes are likely to be rejected in order to reduce code churn.
4. Familiarize yourself with our [release flow](LOTUS_RELEASE_FLOW.md) to understand how changes are incorporated into releases.

## Implementing Changes

Expand Down
Loading
Loading