Skip to content

Minor grammar fixes #1

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

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Minor grammar fixes #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b95fba2
Minor grammar fixes
ecassady Sep 11, 2019
7c3996a
Another minor textual fix.
ecassady Sep 13, 2019
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
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
# git-series

An intelligent way to manage multiple concurrently-deployed releases using
in git.
git.

## Motivation

I've used git-flow for a long time. It's great if you have a simple project
that always only has one version deployed. In my experience, it happens more
often than not that there are more than one version in production. Before
you say "well, you write crappy old-school software," allow me to say that
one of those situtation is multiple containerized microservices sharing
one of those situtations is multiple containerized microservices sharing
a common library. Since these microservices are isolated from each
other, they can choose to use whatever version of the library they desire.
It's possible (maybe even likely) that the team maintaining one of those
Expand Down Expand Up @@ -253,7 +253,7 @@ relation with its predecessor series.

Realize that this does not imply that the change must be incorporated into
all future releases, just that you must make a decision and record it
within the `git` metadata. Propagation the process of maintaining this
within the `git` metadata. Propagation is the process of maintaining this
invariant. For more details, see the [_Propagation_](#Propagation) section.

> Note: These is not _really_ an invariant. It's an "eventually consistent."
Expand Down