diff options
| -rw-r--r-- | docs/release-process.md | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/docs/release-process.md b/docs/release-process.md index 43209eb0..3373aae6 100644 --- a/docs/release-process.md +++ b/docs/release-process.md | |||
| @@ -83,7 +83,8 @@ control how repo finds updates: | |||
| 83 | * `--repo-rev`: This tells repo which branch to use for the full project. | 83 | * `--repo-rev`: This tells repo which branch to use for the full project. |
| 84 | It defaults to the `stable` branch (`REPO_REV` in the launcher script). | 84 | It defaults to the `stable` branch (`REPO_REV` in the launcher script). |
| 85 | 85 | ||
| 86 | Whenever `repo sync` is run, repo will check to see if an update is available. | 86 | Whenever `repo sync` is run, repo will, once every 24 hours, see if an update |
| 87 | is available. | ||
| 87 | It fetches the latest repo-rev from the repo-url. | 88 | It fetches the latest repo-rev from the repo-url. |
| 88 | Then it verifies that the latest commit in the branch has a valid signed tag | 89 | Then it verifies that the latest commit in the branch has a valid signed tag |
| 89 | using `git tag -v` (which uses gpg). | 90 | using `git tag -v` (which uses gpg). |
| @@ -95,6 +96,11 @@ If that tag is valid, then repo will warn and use that commit instead. | |||
| 95 | 96 | ||
| 96 | If that tag cannot be verified, it gives up and forces the user to resolve. | 97 | If that tag cannot be verified, it gives up and forces the user to resolve. |
| 97 | 98 | ||
| 99 | ### Force an update | ||
| 100 | |||
| 101 | The `repo selfupdate` command can be used to force an immediate update. | ||
| 102 | It is not subject to the 24 hour limitation. | ||
| 103 | |||
| 98 | ## Branch management | 104 | ## Branch management |
| 99 | 105 | ||
| 100 | All development happens on the `main` branch and should generally be stable. | 106 | All development happens on the `main` branch and should generally be stable. |