Closed acatangiu closed 3 weeks ago
What is the plan with these project boards? Do you need them for project planning?
We could probably create a bot to keep them in sync with the data from here https://github.com/paritytech/release-registry/
It's a proposal for tracking release relevant dates and included features. If we deem it useful, we can either automate it as you say or keep it manual as it is minimal effort IMO, just copy previous board and update fields for every new planned release (a couple minutes once a month).
(This is an experiment to try and coordinate comms inside & outside of Parity, please put feedback about improvements)
The release is cut-off and now being tested. The release draft can be found here. It is planned to be published on the 25th.
@paritytech/parachains-core please start monitoring the burn-in deployments for abnormalities. Tracking issue https://github.com/paritytech/devops/issues/3539.
@paritytech/appsec please continue with the auditing and prioritization or the changes since the last release.
@SBalaguer @albertogallini @IkerAlus @Imod7 @ottovlotto the preliminary CHANGELOG for preparing announcements is attached below.
This release contains the changes from `polkadot-stable2407-2` to `v1.16.0-rc1`.
## Changelog
### Changelog for `Node Dev`
**ℹ️ These changes are relevant to:** Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
#### [#5410]: Reactive syncing metrics
Syncing metrics are now updated immediate as changes happen rather than every 1100ms as it was happening before.
This resulted in minor, but breaking API changes.
#### [#5288]: Added `polkadot-parachain-lib` helper library that can be used to build a parachain node
This PR adds the `polkadot-parachain-lib` helper library that can be used to build a parachain node.
#### [#4993]: Added BEEFY equivocation-related methods to BeefyApi
This PR adds the `generate_ancestry_proof`, `submit_report_fork_voting_unsigned_extrinsic` and
`submit_report_future_block_voting_unsigned_extrinsic` to `BeefyApi` and bumps the `BeefyApi` version
from 4 to 5.
#### [#5393]: Allow to enable full PoV size
A feature is introduced allowing a collator to enable full PoV size at compile time.
WARNING: To use this feature, security considerations must be understood and the latest
SDK version must be used.
#### [#5065]: Replace env_logger with sp_tracing
This PR replaces env_logger with sp_tracing because of an issue with env_logger and gum #4660
#### [#5344]: Fix storage weight reclaim bug.
Improvement in slot worker loop that will not call create inherent data providers if the major sync is in progress. Before it was called every slot and the results were discarded during major sync.
#### [#5396]: Simplify `SyncingEngine::new()`
Tiny changes to simplify the internal implemenation of API `SyncingEngine::new()` to prevent panics while fetching the genesis hash and to eliminate unnecessary allocation for reserved peers.
#### [#4845]: Make approval-distribution logic runnable on a separate thread
Pass SubsystemSender
The current release candidate is released as pre-release so that it will be available for the external teams to test. The westend
, roccoco
and their parachains are updated to this rc version as well:
The current release candidate is released as pre-release so that it will be available for the external teams to test. The
westend
,roccoco
and their parachains are updated to this rc version as well:
The polkadot node for Rococo and Westend does not seem to be updated is that just a miss or is it work in progress ?
It is work in progress yet
What is actually planned in the QA Testing
phase. Is there a test plan for it ?
What is actually planned in the
QA Testing
phase. Is there a test plan for it ?
There is no testing plan, but it would be good to have one, yes. The only thing we do now is to update the nodes&runtimes and then wait if someone reports a bug.
Do you have something specific in mind? Maybe stress testing the node internally or so?
The only thing we do now is to update the nodes&runtimes and then wait if someone reports a bug.
This probably is enough, but it depends on how much external teams actually test.
Do you have something specific in mind? Maybe stress testing the node internally or so?
One thing that we could do is burn-in the release candidate on a few Kusama validators.
I found small bug in stable2409 release: https://github.com/paritytech/polkadot-sdk/issues/5677
The only thing we do now is to update the nodes&runtimes and then wait if someone reports a bug.
The first bug was reported. ^
Is this the correct place to post bugs, or do we have a better place for that?
Is this the correct place to post bugs, or do we have a better place for that?
Yes this is perfect, thanks 😄
I found small bug in stable2409 release: #5677
We should also put #5677 on stable2409
s project board if we want/need to fix it in this release.
@EgorPopelyaev @BulatSaif what is the status of the nodes being upgraded?
Please post updates in here - if any.
@EgorPopelyaev @BulatSaif what is the status of the nodes being upgraded? Please post updates in here - if any.
Most of the nodes were upgraded as requested by https://github.com/paritytech/devops/issues/3539. You can check the version in Telemetry.
However, RPC nodes (Kusama and Polkadot) were not updated because the new version exposes unsafe RPC methods by default. This issue has already been fixed in https://github.com/paritytech/polkadot-sdk/pull/5678.
Most of the nodes were upgraded as requested by https://github.com/paritytech/devops/issues/3539. You can check the version in Telemetry.
Both Westend and Rococo relay chain node don't seem to have been updated, shouldn't we updating those as well ?
Most of the nodes were upgraded as requested by paritytech/devops#3539. You can check the version in Telemetry.
Both Westend and Rococo relay chain node don't seem to have been updated, shouldn't we updating those as well ?
Yes, it should. I have reopened the issue.
Westend should be updated now @alexggh
Parent issue tracking the
stable2409
long term support release.This issue is used to track the lifecycle of the release. See Polkadot-SDK Release Calendar.
Features included in this release can be tracked under the Stable2409 LTS Release project view.