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.

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

submitting-changes.chapter.md: explain *why* we have three branches #225920

Merged
1 commit merged into from Jul 12, 2023
Merged

submitting-changes.chapter.md: explain *why* we have three branches #225920

1 commit merged into from Jul 12, 2023

Commits on Jun 29, 2023

  1. submitting-changes.chapter.md: explain *why* we have three branches

    The manual does an okay job of explaining the rules for each of the
    three development branches, but really doesn't give any intuition as
    to why there are three (why not four? or two?) or how we got where
    we are today.
    
    This commit attempts to fix that, by explaining that there is one
    branch that allows mass-rebuild commits, and it has a fast-building
    branch both upstream and downstream of it (from the perspective of
    automated merges).
    
    I have also removed the term "stabilization" from the arc labels.
    This vague term is not defined anywhere, and does communicate any
    useful information without a longer explanation.  Therefore it is
    not appropriate for use in a diagram.
    
    Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
    Adam Joseph and fricklerhandwerk committed Jun 29, 2023
    Configuration menu
    Copy the full SHA
    b3fa79b View commit details
    Browse the repository at this point in the history