Skip to content
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

v0.36.0-old #3748

Closed
philknows opened this issue Feb 11, 2022 · 2 comments
Closed

v0.36.0-old #3748

philknows opened this issue Feb 11, 2022 · 2 comments
Assignees
Labels
epic Issues used as milestones and tracking multiple issues.
Milestone

Comments

@philknows
Copy link
Member

philknows commented Feb 11, 2022

This issue tracks significant inclusions and status of fixes + features of the next upcoming release:

Problem (Issue) Solutions (PR) Urgency Merged? Impact/Notes
#3548 #3661 High Yes Improvements to Lodestar: peer scoring cache, fast msg id, etc.
#3523 #3522 Medium No Enable users to manage keystores
#3688 #3753 High Yes For Wagyu Installer: Allow to pass password as a file path, and ensure it's not interactive.
#3428 High Closed The next sync committee branch should be created against the post-state of the finalized checkpoint block.
#3495 High Yes The light-client server should not prepare updates during sync
#3732 #3738 High Yes Fix for performance regression
#3749 #3745 High Yes Fix for performance regression
N/A #3595 High Yes Data loss from Circular Reference objects being dumped
#3760 High No SSZ Upgrade

Linked milestone https://github.com/ChainSafe/lodestar/milestone/13

@philknows philknows added the epic Issues used as milestones and tracking multiple issues. label Feb 11, 2022
@philknows philknows self-assigned this Feb 11, 2022
@dapplion dapplion pinned this issue Feb 18, 2022
@dapplion dapplion added this to the v0.35.0 milestone Feb 18, 2022
@philknows philknows changed the title v0.35.0 v0.36.0 Mar 1, 2022
@philknows
Copy link
Member Author

Bumped this tracker from 0.35.0 to 0.36.0 release.
Decision was made to push 0.35.0 earlier without these planned merges to fix important bug described in #3700 persisting in 0.34.0.

@philknows philknows mentioned this issue Apr 5, 2022
@philknows
Copy link
Member Author

Tasks in this old release milestone are complete, but blocked on other issues for a stable release. Closing in favour of #3884.

@philknows philknows changed the title v0.36.0 v0.36.0-old Apr 5, 2022
@philknows philknows unpinned this issue Apr 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Issues used as milestones and tracking multiple issues.
Projects
None yet
Development

No branches or pull requests

2 participants