Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Switching to stable-track #11377

Merged
merged 26 commits into from
Jan 22, 2020
Merged

Switching to stable-track #11377

merged 26 commits into from
Jan 22, 2020

Conversation

General-Beck
Copy link
Contributor

remove beta from building scripts
stable = latest

@General-Beck General-Beck added A0-pleasereview 🤓 Pull request needs code review. M1-ci 🙉 Continuous integration. labels Jan 10, 2020
@General-Beck General-Beck self-assigned this Jan 10, 2020
@s3krit
Copy link
Contributor

s3krit commented Jan 10, 2020

LGTM. Will keep this open until we are ready to switch to a single release track

Copy link
Collaborator

@TriplEight TriplEight left a comment

Choose a reason for hiding this comment

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

Don't you think that it also makes sense to remove "nightly" as well?
I searched "beta" in code and found more mentions than changed here:

➤ rg beta -g '!*.md'
parity/configuration.rs
984:                            "beta" => ReleaseTrack::Beta,
1517:           let conf2 = parse(&["parity", "--no-download", "--auto-update=all", "--release-track=beta", "--auto-update-delay=300", "--auto-update-check-frequency=100"]);

scripts/gitlab/publish-snap.sh
14:  beta) export GRADE="stable" CHANNEL="beta";;

scripts/gitlab/test-linux.sh
2:# ARGUMENT $1 Rust flavor to run test with (stable/beta/nightly)

scripts/gitlab/rust-changes.sh
10:  (beta|stable)

util/version/Cargo.toml
11:# This versions track. Should be changed to `stable` or `beta` when on respective branches.

parity/cli/mod.rs
299:                    "Set which release track we should use for updates. TRACK can be one of: stable - Stable releases; beta - Beta releases; nightly - Nightly releases (unstable); testing - Testing releases (do not use); current - Whatever track this executable was released on.",

updater/src/types/release_track.rs
41:                     ReleaseTrack::Beta => "beta",
53:                     "beta" => ReleaseTrack::Beta,
104:            assert_eq!(ReleaseTrack::Beta, "beta".into());
113:            assert_eq!("beta", ReleaseTrack::Beta.to_string());

scripts/docker/hub/publish-docker.sh
26:    "beta")
27:        echo "Docker TAGs - 'parity/parity:beta', 'parity/parity:latest', \
32:            --tag "parity/parity:beta" \
36:        docker push "parity/parity:beta";

util/network/src/client_version.rs
461:    pub fn client_capabilities_when_parity_beta_version_then_not_handles_large_requests_true() {
465:                    "2.4.0-beta",

util/network-devp2p/src/ip_utils.rs
36:/// Socket address extension for rustc beta. To be replaces with now unstable API

util/version/src/lib.rs
33:// ^^^ should be reset in Cargo.toml to "stable" or "beta" according to the release branch.

rpc/src/v1/tests/mocked/parity_set.rs
94:     let response = r#"{"jsonrpc":"2.0","result":{"binary":"0x00000000000000000000000000000000000000000000000000000000000005e6","fork":15100,"is_critical":true,"version":{"hash":"0x0000000000000000000000000000000000000097","track":"beta","version":{"major":1,"minor":5,"patch":1}}},"id":1}"#;

rpc/src/v1/tests/mocked/parity.rs
133:    let response = r#"{"jsonrpc":"2.0","result":{"hash":"0x0000000000000000000000000000000000000096","track":"beta","version":{"major":1,"minor":5,"patch":0}},"id":1}"#;
143:    let response = r#"{"jsonrpc":"2.0","result":{"fork":15100,"minor":null,"this_fork":15000,"track":{"binary":"0x00000000000000000000000000000000000000000000000000000000000005e6","fork":15100,"is_critical":true,"version":{"hash":"0x0000000000000000000000000000000000000097","track":"beta","version":{"major":1,"minor":5,"patch":1}}}},"id":1}"#;

@TriplEight
Copy link
Collaborator

@s3krit don't forget to edit README, it also mentions beta

Copy link
Collaborator

@dvdplm dvdplm left a comment

Choose a reason for hiding this comment

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

When this lands, will we still be able to make auto releases for the current parity versions?

parity/cli/mod.rs Show resolved Hide resolved
@s3krit
Copy link
Contributor

s3krit commented Jan 13, 2020

Don't you think that it also makes sense to remove "nightly" as well?
I searched "beta" in code and found more mentions than changed here:

@TriplEight I don't see any reason to remove nightly releases, no. I don't have any numbers on how many people are on the nightly track, but the nightly release publishing doesn't really incur any additional overhead in terms of publishing the release (i.e., it is all done hands-off via CI jobs etc).

@TriplEight
Copy link
Collaborator

Well, what we do here is getting rid of "beta" everywhere, right? We are not removing nightly.
And apparently it involves some changes on Rust.

Co-Authored-By: Denis Pisarev <denis.pisarev@parity.io>
@ordian ordian added this to the 2.7 milestone Jan 13, 2020
@@ -1512,10 +1510,8 @@ mod tests {
#[test]
fn should_parse_updater_options() {
// when
let conf0 = parse(&["parity", "--release-track=testing"]);
let conf1 = parse(&["parity", "--auto-update", "all", "--no-consensus", "--auto-update-delay", "300"]);
let conf2 = parse(&["parity", "--no-download", "--auto-update=all", "--release-track=beta", "--auto-update-delay=300", "--auto-update-check-frequency=100"]);
Copy link
Contributor

Choose a reason for hiding this comment

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

If we're removing these, we also need to remove the asserts just below in this file. This is leading to tests being broken: https://gitlab.parity.io/parity/parity-ethereum/-/jobs/356325

s3krit
s3krit previously approved these changes Jan 20, 2020
@s3krit s3krit dismissed their stale review January 20, 2020 14:08

Found further issues - test-linux fails

util/version/Cargo.toml Outdated Show resolved Hide resolved
@ordian
Copy link
Collaborator

ordian commented Jan 20, 2020

could you merge with master, the diff is quite noisy

Copy link
Collaborator

@ordian ordian left a comment

Choose a reason for hiding this comment

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

The changes look sane to me. I wonder what would happen to the beta track with the autoupdater on? Will the nodes fail to update silently? Might be worth communicating this in the release notes.

@s3krit
Copy link
Contributor

s3krit commented Jan 22, 2020

The changes look sane to me. I wonder what would happen to the beta track with the autoupdater on? Will the nodes fail to update silently? Might be worth communicating this in the release notes.

The actual answer is 'nothing', since no releases in a beta branch will happen again, so the publish-onchain job will never run on the beta branch, so no updates for beta will be pushed on-chain. And yeah correct, gonna reach out and communicate very clearly that those on beta will need to switch to stable to continue getting updates, and those running stable will be upgrading 2 minor versions, which necessitates a db migration, thus they can't just switch back to v2.5

Copy link
Collaborator

@TriplEight TriplEight left a comment

Choose a reason for hiding this comment

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

LGTM!

parity/cli/mod.rs Show resolved Hide resolved
@s3krit s3krit merged commit e1d06ef into master Jan 22, 2020
s3krit added a commit that referenced this pull request Jan 22, 2020
* sccache "stop server" - > "show stats"

* remove testing and beta from update, cli, etc.

* Beta->Nigthly updater

* Beta->Nightly

* ->Nightly and fix

* updater ->Stable

* Testing->Nightly

* Update scripts/gitlab/test-linux.sh

Co-Authored-By: Denis Pisarev <denis.pisarev@parity.io>

* sccache "stop server" - > "show stats"

* remove testing and beta from update, cli, etc.

* Beta->Nigthly updater

* Beta->Nightly

* ->Nightly and fix

* updater ->Stable

* Testing->Nightly

* Update scripts/gitlab/test-linux.sh

Co-Authored-By: Denis Pisarev <denis.pisarev@parity.io>

* Update CHANGELOGs and version

* temporarily allow darwin and windows to be built on any branch

* fix check-benches job

* Revert "temporarily allow darwin and windows to be built on any branch"

This reverts commit 45c72f6.

* fix check-benches job

* Revert changing track from `nightly` to `stable`

* fix test: rpc_parity_upgrade_ready

* fix tests: rpc_parity_version_info, rpc_parity_releases_info

Co-authored-by: Denis Pisarev <denis.pisarev@parity.io>
Co-authored-by: s3krit <pugh@s3kr.it>
Copy link
Collaborator

@dvdplm dvdplm left a comment

Choose a reason for hiding this comment

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

minor grumbles

This release stabilises the 2.5 branch.

As of today, Parity-Ethereum 2.4 reaches end of life and everyone is
encouraged to upgrade.

## Parity-Ethereum [v2.5.4](https://github.com/paritytech/parity-ethereum/releases/tag/v2.5.4)

Parity Ethereum v2.5.4-stable is a security update that addresses servo/rust-smallvec#148
Parity Ethereum v2.5.4-beta is a security update that addresses servo/rust-smallvec#148
Copy link
Collaborator

Choose a reason for hiding this comment

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

Was this really a beta release?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yep. I believe it was a typo originally that marked v2.5.4 as stable. We didn't stabilise v2.5 until v2.5.5: https://github.com/paritytech/parity-ethereum/releases/tag/v2.5.5

@@ -49,8 +49,6 @@ impl Into<ConsensusCapability> for CapState {
pub enum ReleaseTrack {
/// Stable track.
Stable,
/// Beta track.
Beta,
/// Nightly track.
Nightly,
/// Testing track.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there a reason we keep Testing here but remove it from updater/src/types/release_track.rs? Should we remove it here too?

scripts/docker/hub/publish-docker.sh Show resolved Hide resolved
@s3krit s3krit deleted the stable-track branch January 27, 2020 17:00
dvdplm added a commit that referenced this pull request Jan 29, 2020
…pstream

* master:
  Add POSDAO transition and malice report queue. (#11245)
  update master/nightly version: v2.8.0 (#11419)
  ethcore/res: remove morden testnet (#11392)
  fix: export hardcoded sync format (#11416)
  update hardcoded headers: mainnet and ropsten (#11414)
  AuthorityEngine: Minor cleanups. (#11408)
  Update POA bootnodes (#11411)
  Add EtherCore support (#11402)
  verification: fix race same block + misc (#11400)
  Update ProgPoW to 0.9.3 (#11407)
  update classic testnet bootnodes (#11398)
  dependencies: bump `derive_more v0.99` (#11405)
  engine error: remove faulty/unused `From` (#11404)
  Switching to stable-track (#11377)
  ethcore/res: fix ethereum classic chainspec blake2_f activation block num (#11391)
  Update copyright notice 2020 (#11386)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-pleasereview 🤓 Pull request needs code review. M1-ci 🙉 Continuous integration.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants