-
Notifications
You must be signed in to change notification settings - Fork 784
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
Deneb review #4676
Comments
I've added my initials to a few parts that I'd like to review. I'll try to do that shortly. |
I've just added a few things that I know I'll get done before I go on leave. Hopefully I can pick up some more things too. |
I've also put my initials for a few things. I'm also tentatively thinking of looking into the |
Threw some age's in there too |
In #4678 I've reviewed:
|
I've put my initials to the remaining unassigned ones. |
I've done reviewing the |
so I heard deneb merge is imminent. Guys if you had asked me to review the networking part I would have done so Result would have probable been that it must be ❇️ perfect ❇️ since I know you've put to much effort into it |
I've finished reviewing the parts I was assigned. Happy to merge! |
I also finished off the slab assigned to Mac, and re-reviewed I think we are good to merge. We can address remaining feedback on If you have unresolved review comments, please open an issue (or PR) to resolve them on Consider this the FINAL CALL before Deneb is merged to unstable. If you've noticed any show-stoppers, please raise them now! |
## Issue Addressed Related to #4676. Deneb-specifc CI code to be removed before merging to `unstable`. Dot not merge until we're ready to merge into `unstable`, as we may need to release deneb docker images before merging. Keep in mind that most of the changes in the below PR (to `unstable`) have already been merged to `deneb-free-blobs`, so merging `deneb-free-blobs` into `unstable` would include those changes - it would be ok if the release runners are ready, otherwise we may want to exclude them before merging. - #4592
## Issue Addressed Related to sigp#4676. Deneb-specifc CI code to be removed before merging to `unstable`. Dot not merge until we're ready to merge into `unstable`, as we may need to release deneb docker images before merging. Keep in mind that most of the changes in the below PR (to `unstable`) have already been merged to `deneb-free-blobs`, so merging `deneb-free-blobs` into `unstable` would include those changes - it would be ok if the release runners are ready, otherwise we may want to exclude them before merging. - sigp#4592
done! #4054 appreciate the huge review team effort !!! 🙏 🎉 |
Description
I've been reviewing #4054 for a few days and I'm coming to the realisation that I can't review it alone. It's a 22k line diff across 250 files. I estimate it would take about 1.5 weeks full-time and I can't do any one task full-time anymore. Even if I were to get 50% of uninterrupted time (very optimistic), then it's going to take 3 weeks. Given that I'm away for 2+ weeks next week, we're looking at over a month of Deneb review. Furthermore, I think we need more that one person to review such a large change to give a decent quality assurance.
So, in the interests of getting #4054 merge into
unstable
expediently, I propose that we split up the review.Splitting the Review
In the table below I've split the review into components with a lil' script.
I'd like to ask the full-time Lighthouse developers to identify components which:
And then add their name to the "Reviewer" column (if you don't have perms to edit my post, just comment and someone with perms will update it). The "Status" column can be updated when the review is complete.
Some additional thoughts:
./consensus
could use a couple of eyes).deneb-free-blobs
) then it would make sense to assign yourself to that component and only review the un-reviewed changes (i.e., don't double-review things).Components and Assignments
The text was updated successfully, but these errors were encountered: