diff options
| author | luigi1111 <luigi1111w@gmail.com> | 2019-09-24 10:30:00 -0500 |
|---|---|---|
| committer | luigi1111 <luigi1111w@gmail.com> | 2019-09-24 10:30:00 -0500 |
| commit | f15eded8d7a9299730f802e8692fc668c93bfcfe (patch) | |
| tree | e93a9a5b9cb7d6fba8899d55647d681d71d52d17 | |
| parent | Merge pull request #5884 (diff) | |
| parent | README: fix master branch spelling, it is not Master (diff) | |
| download | monero-f15eded8d7a9299730f802e8692fc668c93bfcfe.tar.xz | |
Merge pull request #5886
ae32862 README: fix master branch spelling, it is not Master (moneromooo-monero)
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -159,7 +159,7 @@ X's indicate that these details have not been determined as of commit date. ## Release staging schedule and protocol -Approximately three months prior to a scheduled software upgrade, a branch from Master will be created with the new release version tag. Pull requests that address bugs should then be made to both Master and the new release branch. Pull requests that require extensive review and testing (generally, optimizations and new features) should *not* be made to the release branch. +Approximately three months prior to a scheduled software upgrade, a branch from master will be created with the new release version tag. Pull requests that address bugs should then be made to both master and the new release branch. Pull requests that require extensive review and testing (generally, optimizations and new features) should *not* be made to the release branch. ## Compiling Monero from source |