Next Release tracking issue

[gnunicorn]

We want to make a new full feature release, especially to get the new FRAME into the hands of people. As of now, the strategy is to release all crates with code changes since 2.0 under the correct SemVer-version, so some will be patches others minor some major upgrades.

Big picture changes (why we are releasing):

• this brings FRAME 2.0 macros
• FRAME: Ref-Counting Provider Provider ref count #7343
• New Pallet: Participation Lottery Pallet Participation Lottery Pallet #7221

Please link in this (with checklist here) any blocking issues or PRs, that are being worked on and expected to be merged within the next 2 weeks latest , including a mention of the person responsible (as shown):

• cleaning up dependencies clean up dependencies for next release #7956 @gnunicorn
• updating to SCALE 2.0 Update parity-scale-codec to 2.0 #7994 @thiolliere

[liuchengxu]

Please include #7127 in the next release.
Edit: Done ✔️

[xlc]

I would like to have #7778 if possible

[gui1117]

we should also include incoming release of parity-scale-codec 2.0

[gnunicorn]

@thiolliere is this expected to happen within the next 10 days? Is there a tracking issue for it?

[gui1117]

Yes it is expected to happen next week, there is only one PR left https://github.com/paritytech/parity-scale-codec/milestone/3

[apopiak]

I would like to get these 2 quality of life PRs in: #8017 and #8019
Edit: Done ✔️

[gui1117]

not sure it is required to next release, but #7949 can be good to have

EDIT: we should be able to finish it very soon like 1 or 2 days

[bkchr]

Telemetry is broken: #8093

[gnunicorn]

closed by #8098

[liuchengxu]

Why no release for sc-finality-grandpa-wrap-sync? https://crates.io/search?page=1&per_page=10&q=sc-finality-grandpa-wrap-sync

And the version is still 0.8.0:

substrate/client/finality-grandpa-warp-sync/Cargo.toml

Line 4 in 49a4103

version = "0.8.0"

[gnunicorn]

@liuchengxu it is marked as publish = false by its authors:

https://github.com/paritytech/substrate/blame/3957f43912e43fd28b624bb0736141ac24b51615/client/finality-grandpa-warp-sync/Cargo.toml#L8

I presume because it is far from ready yet, but would leave it to @expenses to elaborate on that.

[expenses]

I presume because it is far from ready yet, but would leave it to @expenses to elaborate on that.

Personally, I think the crate is ready-enough at the moment. The core part of grandpa warp sync is in sc-finality-grandpa anyway; the request response handler is pretty simple. I think publish = false is just there because I copied it from somewhere else 😅

[liuchengxu]

@gnunicorn @expenses If the code is ready, is there any chance that we can still have it published in the Substrate 3.0 release? It just does not look perfect with only one git dep left in the Cargo.toml as we normally use version = "3.0.0"/"0.9.0" in the project.