-
Notifications
You must be signed in to change notification settings - Fork 32
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
Enforce OEP-1 clause that all OEPs should be merged even if rejected/withdrawn #428
Comments
Unassigning myself as I have no current plans to do this. |
@kdmccormick for this one, would you suggest I go through all unmerged PRs and reopen and merge them with an appropriate status? |
That's what OEP-1 says to do. Personally, I think it's a little silly. If I wanted to know the rejected OEPs, I could just look at closed PRs. |
I think I do see the sense in it, because most people don't go through closed PRs. I think I'll take this on |
Reflect reality that rejected or withdrawn proposals are frequently left unmerged even though OEP-1 had previously called for it. Addresses #428
Ultimately I agree with you, @kdmccormick . I don't think it's worth the time to merge PRs that never materialized. I updated OEP-1 accordingly and discussion can continue on #601 |
Reflect reality that rejected or withdrawn proposals are frequently left unmerged even though OEP-1 had previously called for it. Addresses #428
Reflect reality that rejected or withdrawn proposals are frequently left unmerged even though OEP-1 had previously called for it. Addresses #428
Reflect reality that rejected or withdrawn proposals are frequently left unmerged even though OEP-1 had previously called for it. Addresses #428
Reflect reality that rejected or withdrawn proposals are frequently left unmerged even though OEP-1 had previously called for it. Addresses openedx#428
The text was updated successfully, but these errors were encountered: