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

Land FEVM actor work into master #1023

Closed
4 of 6 tasks
jennijuju opened this issue Jan 12, 2023 · 1 comment
Closed
4 of 6 tasks

Land FEVM actor work into master #1023

jennijuju opened this issue Jan 12, 2023 · 1 comment
Assignees

Comments

@jennijuju
Copy link
Member

jennijuju commented Jan 12, 2023

@arajasek Proposed steps:

  • (Unrelated, just cleanup): Finish landing chore: merge release/v1.20.0 into master lotus#10030
  • Merge built-in actors master into next
  • Check whether the Send changes can land in master, land them if so
    .
    ...(items are vague past this point, will get clarified)
    .
  • Look for more non-FIPpy changes in next that can be extracted into master
  • As FIPs get accepted (esp smaller ones), start landing them
  • As FIPs move towards being accepted, extract out the changes in PRs and get review (we can block merge on acceptance)

ORIGINAL ISSUE:

there will be quite some work needed to get PR extracted from next branch and gradually lands them into master

and given this would be the first time for some actor maintainers to thoroughly review the code, we shall expect at least 1 week for the review & feedback address cycle.

According to the current targeted code freeze date, Jan 26th, I think the PR creation needs to start at the latest by Jan 18th.

@jennijuju jennijuju added the P0 label Jan 12, 2023
@maciejwitowski maciejwitowski removed the P0 label Jan 12, 2023
@maciejwitowski maciejwitowski transferred this issue from filecoin-project/builtin-actors Jan 12, 2023
@maciejwitowski maciejwitowski transferred this issue from filecoin-project/ref-fvm Jan 12, 2023
@maciejwitowski maciejwitowski assigned arajasek and unassigned Stebalien Jan 19, 2023
@maciejwitowski
Copy link
Contributor

The current targeted code freeze date is Feb 2nd. We want to start this on Jan 23rd-24th to allocate more time. cc @arajasek

@jennijuju jennijuju moved this from 🌟 In Scope to 🏗 In progress in Network v18 Feb 6, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Network v18 Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

No branches or pull requests

4 participants