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
I found it really helpful when @dtolnay assigned me to rust-lang/rust#115333 after I proposed fcp merge. This caused the PR notifications to show up in my "assigned" category and reinforced that I was the lang team member "shepherding" it through.
Additionally, when we manually merge RFCs and PRs after FCP is complete, we usually leave it up to the person who started the FCP.
I think we should automate and formalize this by having triagebot assign the FCP proposer.
The text was updated successfully, but these errors were encountered:
Additionally, when we manually merge RFCs and PRs after FCP is complete, we usually leave it up to the person who started the FCP.
Do we? I was involved in several FPCs on implementation-heavy PRs. Review is usually done by someone from the compiler team, but it needs t-lang FCP so the FCP proposer is a t-lang member.
I think there are many PRs where assigning the FCP proposer does not make a lot of sense.
I found it really helpful when @dtolnay assigned me to rust-lang/rust#115333 after I proposed fcp merge. This caused the PR notifications to show up in my "assigned" category and reinforced that I was the lang team member "shepherding" it through.
Additionally, when we manually merge RFCs and PRs after FCP is complete, we usually leave it up to the person who started the FCP.
I think we should automate and formalize this by having triagebot assign the FCP proposer.
The text was updated successfully, but these errors were encountered: