It seems like adding an "r: stale" or "r: unresponsive" tag might be a
better approach with more support then, and we could have it written in
the developer guide how long after changes are requested this tag should
be applied. Then anyone who is looking to pickup unfinished work can
search for that tag, and anyone who in interested in the PR being merged
will know that it's probably not coming soon unless someone else steps
up to finish it. I think Dima's suggestion of 6 months is good, but if
we aren't closing the PR then maybe even 3 months is sufficient. The "r:
stale" tag can be viewed as saying that other people should feel free to
take over the PR (preferably after checking with the original author if
they were planning on finishing it soon, in case they were about to
start work on it again or if they have any objection to or advice for
someone else finishing their work).
If someone does pickup a stale PR and opens a new PR based on it, should
the stale PR be closed when the new PR is opened, or when the new PR is
merged? I lean towards when it's opened unless someone can think of a
reason to keep open PRs for multiple iterations of the same thing.
Vincent Macri (He/Him)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/sage-devel/8da7e1d9-22cc-420c-a3d2-b131b49fc1cb%40ucalgary.ca.
