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

Monorepo: Make Merge Default Hardfork #2015

Closed
holgerd77 opened this issue Jul 5, 2022 · 2 comments · Fixed by #2087
Closed

Monorepo: Make Merge Default Hardfork #2015

holgerd77 opened this issue Jul 5, 2022 · 2 comments · Fixed by #2087

Comments

@holgerd77
Copy link
Member

Since we are now getting so close to the Merge HF date with our breaking releases (or might be even do after the Merge, we'll see) I would be a big fan of directly making the Merge HF the default HF on the libraries.

There would be a very very tiny window of where we are "ahead" (and even this wouldn't be bad), and otherwise we would be aligned with the current HF during very much most of the time of the release lifecycle. 🙂

Inspiration and guidance for update locations can be taken from the London HF work #1749 done by @emersonmacro. I would be very much expecting though that this upgrade work is not as extensive any more (but still some work to do), since Emmett hardened e.g. various code parts like test initializations along the way (by explicitly providing a certain HF e.g.).

This doesn't need to be finished before Beta 2 but can e.g. be done if someone gets bored while I am and other are on holidays e.g.. 😅

@g11tech
Copy link
Contributor

g11tech commented Jul 5, 2022

@holgerd77 can put in my bucket! 🙂

@g11tech g11tech self-assigned this Jul 5, 2022
@holgerd77
Copy link
Member Author

@holgerd77 can put in my bucket! 🙂

Oh, my issues really sell like hot cakes today, also #2013 gone in less than 2 hours. 😅

@g11tech Sure, cool! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants