Switching to stable-track#11377
Conversation
|
LGTM. Will keep this open until we are ready to switch to a single release track |
TriplEight
left a comment
There was a problem hiding this comment.
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}"#;
|
@s3krit don't forget to edit README, it also mentions |
dvdplm
left a comment
There was a problem hiding this comment.
When this lands, will we still be able to make auto releases for the current parity versions?
@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). |
|
Well, what we do here is getting rid of "beta" everywhere, right? We are not removing nightly. |
Co-Authored-By: Denis Pisarev <denis.pisarev@parity.io>
Co-Authored-By: Denis Pisarev <denis.pisarev@parity.io>
| // 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"]); |
There was a problem hiding this comment.
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
This reverts commit 45c72f6.
|
could you merge with master, the diff is quite noisy |
The actual answer is 'nothing', since no releases in a |
* 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>
| ## 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 |
There was a problem hiding this comment.
Was this really a beta release?
There was a problem hiding this comment.
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
| Beta, | ||
| /// Nightly track. | ||
| Nightly, | ||
| /// Testing track. |
There was a problem hiding this comment.
Is there a reason we keep Testing here but remove it from updater/src/types/release_track.rs? Should we remove it here too?
…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)
remove
betafrom building scriptsstable=latest