-
Notifications
You must be signed in to change notification settings - Fork 680
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
Parent issue for stable2409
LTS release
#5583
Comments
What is the plan with these project boards? Do you need them for project planning? |
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). |
Status Update(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. Next Steps@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. CHANGELOG
This release contains the changes from ChangelogChangelog for
|
The current release candidate is released as pre-release so that it will be available for the external teams to test. The |
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 |
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. |
This probably is enough, but it depends on how much external teams actually test.
One thing that we could do is burn-in the release candidate on a few Kusama validators. |
I found small bug in stable2409 release: #5677 |
The first bug was reported. ^ Is this the correct place to post bugs, or do we have a better place for that? |
Yes this is perfect, thanks 😄 |
We should also put #5677 on |
@EgorPopelyaev @BulatSaif what is the status of the nodes being upgraded? |
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 #5678. |
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 |
Status UpdateThe release is now out and ready to be used. Next step is for The Fellowship to pick it up and integrate it into the runtimes repo. Full changelog is here. We should update the testnet runtimes and all nodes to the new version. |
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.
The text was updated successfully, but these errors were encountered: