How teams ship

How a change gets from one laptop to every user.

  1. Stop 1, next

    A saved step commit

    Think of it when you finish one small step that works, before you start the next.

    StartAbout 3 minutes. The word for it comes at the end.

  2. Stop 2, next

    A side road for one change branch, merge

    Think of it when you start a change that is not ready for everyone yet, or two people or agents work on the same code at once.

    StartAbout 3 minutes. The word for it comes at the end.

  3. Stop 3, next

    A change asking to join pull request

    Think of it when a change is ready for others to see, check and approve.

    StartAbout 3 minutes. The word for it comes at the end.

  4. Stop 4, next

    Copies of the whole system environments

    Think of it when you test something and must know where the test really ran, or a test could reach real users or real money.

    StartAbout 3 minutes. The word for it comes at the end.

  5. Stop 5, next

    Put it live deploy

    Think of it when a change is about to reach real users, or something broke right after a release.

    StartAbout 3 minutes. The word for it comes at the end.

  6. Stop 6, next

    Ship it switched off feature flag

    Think of it when you want new code live but not yet visible, or you want an off switch for a risky change.

    StartAbout 3 minutes. The word for it comes at the end.