Skip to content
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.

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

Remove migration scripts <=0.38 #9291

Merged
merged 12 commits into from
May 11, 2021
Prev Previous commit
Next Next commit
Include migratio wording
  • Loading branch information
amaury1093 committed May 11, 2021
commit e2b8445e639c226a620e64d21eac2ebe469f03ad
18 changes: 10 additions & 8 deletions STABLE_RELEASES.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,6 @@

Only the following release series are currently supported and receive bug fixes:


* **0.39 «Launchpad»** will be supported until 6 months after **0.42.0** is published. A fairly strict **bugfix-only** rule applies to pull requests that are requested to be included into a stable point-release.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did the minimal changes to add wording for migrations, and remove 0.37 stuff.

However, this doc needs a more general update (see #9189), which is out of scope for this PR.

* **0.42 «Stargate»** is the latest stable release.

Expand All @@ -14,7 +13,7 @@ The **0.42 «Stargate»** release series is maintained in compliance with the **

This policy presently applies *only* to the following release series:

* **0.39 «Launchpad»**
* **0.42 «Stargate»**

### Point Releases

Expand Down Expand Up @@ -46,6 +45,10 @@ priority is to minimise the risk caused by changes that are not strictly require
be correlated with minimising the size of such changes. As such, the same bug may need to be fixed in different
ways in stable releases and `master` branch.

### Migrations

To smoothen the update to the latest stable release, the SDK includes a set of CLI commands for managing migrations between SDK versions, under the `migrate` subcommand. Only migration scripts between stable releases are included. For the current release, **0.39 «Launchpad»** and later migrations are supported.

### What qualifies as a Stable Release Update (SRU)

* **High-impact bugs**
Expand Down Expand Up @@ -84,12 +87,12 @@ As rule of thumb, the following changes will **NOT** be automatically accepted i

## Stable Release Exception - Procedure

1. Check that the bug is either fixed or not reproducible in `master`. It is, in general, not appropriate to release bug fixes for stable releases without first testing them in `master`. Please apply the label [0.39 «Launchpad»](https://github.com/cosmos/cosmos-sdk/labels/0.39%20LTS%20%28Launchpad%29) to the issue.
1. Check that the bug is either fixed or not reproducible in `master`. It is, in general, not appropriate to release bug fixes for stable releases without first testing them in `master`. Please apply the label [0.42 «Stargate»](https://github.com/cosmos/cosmos-sdk/labels/0.42%20LTS%20%28Stargate%29) to the issue.
2. Add a comment to the issue and ensure it contains the following information (see the bug template below):
* **[Impact]** An explanation of the bug on users and justification for backporting the fix to the stable release.
* A **[Test Case]** section containing detailed instructions on how to reproduce the bug.
* A **[Regression Potential]** section with a clear assessment on how regressions are most likely to manifest as a result of the pull request that aims to fix the bug in the target stable release.
3. **Stable Release Managers** will review and discuss the PR. Once *consensus* surrounding the rationale has been reached and the technical review has successfully concluded, the pull request will be merged in the respective point-release target branch (e.g. `release/launchpad/0.39.X` being `X` the Launchpad's upcoming point-release) and the PR included in the point-release's respective milestone (e.g. `0.39.5`).
3. **Stable Release Managers** will review and discuss the PR. Once *consensus* surrounding the rationale has been reached and the technical review has successfully concluded, the pull request will be merged in the respective point-release target branch (e.g. `release/v0.42.x`) and the PR included in the point-release's respective milestone (e.g. `0.42.5`).

### Stable Release Exception - Bug template

Expand All @@ -100,7 +103,7 @@ Brief xplanation of the effects of the bug on users and a justification for back

#### Test Case

Detailed instructions on how to reproduce the bug on Launchpad's most recently published point-release.
Detailed instructions on how to reproduce the bug on Stargate's most recently published point-release.

#### Regression Potential

Expand All @@ -122,8 +125,7 @@ Their responsibilites include:

The Stable Release Managers are appointed by the Interchain Foundation.

*Stable Release Managers* for the **0.39 «Launchpad»** release series follow:
*Stable Release Managers* for the **0.42 «Stargate»** release series follow:

* @alessio - Alessio Treglia
* @clevinson - Cory Levinson-
* @ethanfrey - Ethan Frey
* @clevinson - Cory Levinson