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

Ethereum Core Devs Meeting 113 Agenda #309

Closed
timbeiko opened this issue Apr 30, 2021 · 7 comments
Closed

Ethereum Core Devs Meeting 113 Agenda #309

timbeiko opened this issue Apr 30, 2021 · 7 comments

Comments

@timbeiko
Copy link
Collaborator

timbeiko commented Apr 30, 2021

ACD 113

Meeting Info

Agenda

  1. London Updates
    1. Baikal status & next steps
    2. EIP-3541 Proposal to include EIP-3541 in London #307 (comment)
    3. EIP-3554 (EIP-3238 alternative) Proposal to include EIP-3238 (diff bomb) in London #256 (comment)
    4. JSON RPC Spec Naming (Open PR, Relevant Thread)
    5. Block Numbers London Timing #245 (comment)
  2. Other Discussion Items
    1. (If time permits) Merge/Rayonism updates
    2. 1559 UI Call Announcement by @tvanepps
@jochem-brouwer
Copy link
Member

I am assuming this is part of point 1.iv, but we should definitely discuss if the client freeze on the 19th of May is still ok. We have possibly more EIPs for London and also possible changes to 1559.

@holgerd77
Copy link

Did some kitchen planning how things might go with the current updates and changes:

CW19 (May 10-16): Clients implement/merge new EIPs / 1559 changes (so: next week)
CW20 (May 17-23): Baikal testnet can be launched, testnet running, bug fixes
CW21 (May 24-30): Hopefully stable testnet (Baikal) run

Relevant target dates (taken from here):

Client Freeze: May 19
Clients Release: June 2
First testnet fork (Ropsten): June 9

Just as some orientation for discussion and preparation.

Timeline getting denser, but might still work with the intended client freeze date I would think on first look? 🤔 (actually: what is the intended definition of "client freeze", I guess bug fixes are still "allowed" 😄 , but the spec should be implemented and PRs merged?)

@timbeiko
Copy link
Collaborator Author

timbeiko commented May 6, 2021

The goal of the "client freeze" was to give teams two weeks between any changes and when they need to have a release ready for a blog post announcement for London. At that point, you would hope all the PRs are merged and the only thing that happens are possibly bug fixes.

We definitely need to discuss this on the call based on the progress made, and the decisions taken tomorrow in #308

@lightclient
Copy link
Member

I would be curious to hear an update on the merge testnet and any updated thoughts on the merge timeline.

@timbeiko
Copy link
Collaborator Author

@lightclient agreed - I will add "merge updates" at the end if someone wants to walk through Rayonism and next steps. My hope is we use this call to wrap up London details, and worst case if that takes the entire call, we can focus on the merge in more depth next time.

@tvanepps
Copy link
Collaborator

Only needs to be mentioned briefly: I'm planning a sync call and Resource document for 1559 UIs - if you're a wallet or interface designer, please reach out to me (@ trent_vanepps) to be added to the calendar invite when we have a time chosen

@timbeiko
Copy link
Collaborator Author

Closed in favor of #321

KenMan79 added a commit to KenMan79/ethereum-foundation-pm that referenced this issue May 20, 2021
Transcribe of the Friday, May 14th, 2021 All Core Dev Meeting issue ethereum#309
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants