You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@arajasek Proposed steps:
master
into nextSend
changes can land in master, land them if so.
...(items are vague past this point, will get clarified)
.
next
that can be extracted intomaster
ORIGINAL ISSUE:
there will be quite some work needed to get PR extracted from
next
branch and gradually lands them intomaster
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.
The text was updated successfully, but these errors were encountered: