You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[ ]1. Decide on release designation (are we doing a patch, or minor version bump) and start a P.R. for the release
3
+
-[ ]1. Decide on release designation (are we doing a patch, or minor version bump) and start a branch for the release
4
4
-[ ]2. Add commits/PRs that are desired for this release **that haven’t already been added to develop**
5
5
-[ ]3. Merge items in `PENDING.md` into the `CHANGELOG.md`. While doing this make sure that each entry contains links to issues/PRs for each item
6
6
-[ ]4. Summarize breaking API changes section under “Breaking Changes” section to the `CHANGELOG.md` to bring attention to any breaking API changes that affect RPC consumers.
7
7
-[ ]5. Tag the commit `git tag -a { .Release.Name }-rcN -m 'Release { .Release.Name }'`
8
-
-[ ]6. Open a branch & PR to merge the pending release back into `develop`. If any changes are made to the release branch, they must also be made to the pending develop merge, and both must pass tests.
9
-
-[ ]7. Kick off 1 day of automated fuzz testing
10
-
-[ ]8. Release Lead assigns 2 people to perform [buddy testing script](/docs/RELEASE_TEST_SCRIPT.md) and update the relevant documentation
11
-
-[ ]9. If errors are found in either #6 or #7 go back to #2 (*NOTE*: be sure to increment the `rcN`)
12
-
-[ ]10. After #6 and #7 have successfully completed then merge the release PR and push the final annotated release tag (created with `git tag -a`)
8
+
-[ ]6. Open PRs for both `master` and `develop`. From now onwards ***no additional PRs targeting develop should be merged**. Additional commits can be added on top of the release branch though.
9
+
-[ ]7. Ensure both `master` and `develop` PRs ***pass tests***.
10
+
-[ ]8. Kick off 1 day of automated fuzz testing
11
+
-[ ]9. Release Lead assigns 2 people to perform [buddy testing script](/docs/RELEASE_TEST_SCRIPT.md) and update the relevant documentation
12
+
-[ ]10. If errors are found in either #6 or #7 go back to #2 (*NOTE*: be sure to increment the `rcN`)
13
+
-[ ]11. After #6 and #7 have successfully completed then merge the release PR create the final release annotated tag:
14
+
- `git tag -a -m { .Release.Name } 'Release { .Release.Name }'
15
+
- Merge **the release tag** to both `master` and `develop` so that both branches sit on top of the same commit: `branches='master develop' ; for b in $branches ; do git checkout $b ; git merge { .Release.Name } ; git push $b`.
16
+
Alternatively merge both the aforementioned release PRs.
17
+
- Push the final annotated release tag: `git push --tags`
Copy file name to clipboardExpand all lines: docs/gaia/delegator-guide-cli.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,27 @@ This document contains all the necessary information for delegators to interact
4
4
5
5
It also contains instructions on how to manage accounts, restore accounts from the fundraiser and use a ledger nano device.
6
6
7
+
__Very Important__: Please assure that you follow the steps described hereinafter
8
+
carefully, as negligence in this significant process could lead to an indefinite
9
+
loss of your Atoms. Therefore, read through the following instructions in their
10
+
entirety prior to proceeding and reach out to us in case you need support.
11
+
12
+
Please also note that you are about to interact with the Cosmos Hub, a
13
+
blockchain technology containing highly experimental software. While the
14
+
blockchain has been developed in accordance to the state of the art and audited
15
+
with utmost care, we can nevertheless expect to have issues, updates and bugs.
16
+
Furthermore, interaction with blockchain technology requires
17
+
advanced technical skills and always entails risks that are outside our control.
18
+
By using the software, you confirm that you understand the inherent risks
19
+
associated with cryptographic software (see also risk section of the
20
+
[Interchain Cosmos Contribution terms](https://github.com/cosmos/cosmos/blob/master/fundraiser/Interchain%20Cosmos%20Contribution%20Terms%20-%20FINAL.pdf)) and that the Interchain Foundation and/or
21
+
the Tendermint Team may not be held liable for potential damages arising out of the use of the
22
+
software. Any use of this open source software released under the Apache 2.0 license is
23
+
done at your own risk and on a "AS IS" basis, without warranties or conditions
0 commit comments