📅 Original date posted:2011-09-20
🗒️ Summary of this message: Proposal to add timers to pull requests and issues to avoid abrupt closure. Automated warning emails will be sent before closure.
📝 Original message:On Mon, Sep 19, 2011 at 8:20 PM, Alex Waters <ampedal at gmail.com> wrote:
> I would like to propose adding timers to the pulls / issues:
>
> https://github.com/bitcoin/bitcoin/pull/523
>
> "From time to time a pull request will become outdated. If this occurs, and
> the pull is no longer automatically mergeable; it will be closed after 15
> days. This can be avoided by rebasing the commit. Pull requests closed in this
> manner will have their corresponding issue labeled stagnant.
>
> Non-bug issues with no commits will be closed after 15 days from their
> last activity.
> Issues closed in this manner will be labeled stale.
>
> Requests to reopen closed pull requests and/or issues can be submitted to
> QA at BitcoinTesting.org. "
We need to avoid a user/contributor experience of: "my pull request
was abruptly closed with no warning"
Contributors might not track the state of the tree on a day-to-day
basis. Thus, following the example of bugzilla.redhat.com and many
other "tracker" applications, outdated issues first initiate an
automated warning email -- usually by adding a comment to the bug
report -- that describes the policy, why the policy (closing outdated
reports) exists, and how to avoid automated report closure.
In our case, this means a "we will close pull req, unless you update
this commit in 15 days" comment should be added to the pull req. The
comment should describe in broad terms, with links, how to rebase a
commit, what standard expectations are, etc.
Closing with no warning should be avoided.
--
Jeff Garzik
exMULTI, Inc.
jgarzik at exmulti.com
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 02:28:17
in reply to nevent1q…g8aa
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Seen on
wss://relay.noswhere.comPublished at
2023-06-07 02:28:17Event JSON
{
"id": "dbb5a88f9194090d89acca10c6986f13723ed3b1bb4cfdcd9978c51faae69009",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686104897,
"kind": 1,
"tags": [
[
"e",
"00948366df0b728cc41a2b67effa9a8e54f3a006052331dcb810ba5afefa4b22",
"",
"root"
],
[
"e",
"c25c14a583bd45dc1ea94529957cfd19aa6186bbee795108df35d9a725267966",
"",
"reply"
],
[
"p",
"52d684c703db27d20a0b2e3f7dc21cd09fbb302808a629365699ed800f2515ae"
]
],
"content": "📅 Original date posted:2011-09-20\n🗒️ Summary of this message: Proposal to add timers to pull requests and issues to avoid abrupt closure. Automated warning emails will be sent before closure.\n📝 Original message:On Mon, Sep 19, 2011 at 8:20 PM, Alex Waters \u003campedal at gmail.com\u003e wrote:\n\u003e I would like to propose adding timers to the pulls / issues:\n\u003e\n\u003e https://github.com/bitcoin/bitcoin/pull/523\n\u003e\n\u003e \"From time to time a pull request will become outdated. If this occurs, and\n\u003e the pull is no longer automatically mergeable; it will be closed after 15\n\u003e days. This can be avoided by rebasing the commit. Pull requests closed in this\n\u003e manner will have their corresponding issue labeled stagnant.\n\u003e\n\u003e Non-bug issues with no commits will be closed after 15 days from their\n\u003e last activity.\n\u003e Issues closed in this manner will be labeled stale.\n\u003e\n\u003e Requests to reopen closed pull requests and/or issues can be submitted to\n\u003e QA at BitcoinTesting.org. \"\n\n\nWe need to avoid a user/contributor experience of: \"my pull request\nwas abruptly closed with no warning\"\n\nContributors might not track the state of the tree on a day-to-day\nbasis. Thus, following the example of bugzilla.redhat.com and many\nother \"tracker\" applications, outdated issues first initiate an\nautomated warning email -- usually by adding a comment to the bug\nreport -- that describes the policy, why the policy (closing outdated\nreports) exists, and how to avoid automated report closure.\n\nIn our case, this means a \"we will close pull req, unless you update\nthis commit in 15 days\" comment should be added to the pull req. The\ncomment should describe in broad terms, with links, how to rebase a\ncommit, what standard expectations are, etc.\n\nClosing with no warning should be avoided.\n\n-- \nJeff Garzik\nexMULTI, Inc.\njgarzik at exmulti.com",
"sig": "67fcf14e248fedd2e24ad5757f35516b9c09e4f731bb9f38d5febd6062b886eb1f9fb833c26329e7d4faf64026f679f55ee4255aba903392df02dc829ed5f095"
}