📅 Original date posted:2011-09-20
🗒️ Summary of this message: Refinement needed to avoid abruptly closing pull requests without warning. Suggest automated warning emails and detailed rebase walkthroughs to avoid outdated issues.
📝 Original message:> We need to avoid a user/contributor experience of: "my pull request
> was abruptly closed with no warning"
I agree, I definitely want to go about this in a non-jerk way. I would
be pissed if I spent hours coding something, and it was put on the
back burner and eventually closed (especially without notice). The
wording and process could use refinement.
> 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.
I can definitely do this, and give a wordy notice before I start the
timer. I will write up a message that links to a rebase walkthrough
(any suggestions? I think Gavin has one somewhere...), I would like it
to be more detailed than GitHub's walk-through.
My main reason for pushing this is that it will help clear out some of
the older pulls/issues that exist right now. I'm hoping that in the
future, the QA process will be good enough that pulls/issues won't
fall behind from lack of testing - and the timers will be used very
sparingly. It should only be in place to sort out the pulls/issues
that the majority doesn't want included in the client.
Alex Waters [ARCHIVE] /
npub12t…vf5r2
2023-06-07 02:28:21
in reply to nevent1q…cz6w
Author Public Key
npub12ttgf3crmvnayzst9clhmssu6z0mkvpgpznzjdjkn8kcqre9zkhqmvf5r2Published at
2023-06-07 02:28:21Event JSON
{
"id": "cc7d7e8a378f428e298b1b263de354af87fbc2c47c11b4e62decaa4e675df4b4",
"pubkey": "52d684c703db27d20a0b2e3f7dc21cd09fbb302808a629365699ed800f2515ae",
"created_at": 1686104901,
"kind": 1,
"tags": [
[
"e",
"00948366df0b728cc41a2b67effa9a8e54f3a006052331dcb810ba5afefa4b22",
"",
"root"
],
[
"e",
"dbb5a88f9194090d89acca10c6986f13723ed3b1bb4cfdcd9978c51faae69009",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2011-09-20\n🗒️ Summary of this message: Refinement needed to avoid abruptly closing pull requests without warning. Suggest automated warning emails and detailed rebase walkthroughs to avoid outdated issues.\n📝 Original message:\u003e We need to avoid a user/contributor experience of: \"my pull request\n\u003e was abruptly closed with no warning\"\n\nI agree, I definitely want to go about this in a non-jerk way. I would\nbe pissed if I spent hours coding something, and it was put on the\nback burner and eventually closed (especially without notice). The\nwording and process could use refinement.\n\n\u003e Contributors might not track the state of the tree on a day-to-day\n\u003e basis. Thus, following the example of bugzilla.redhat.com and many\n\u003e other \"tracker\" applications, outdated issues first initiate an\n\u003e automated warning email -- usually by adding a comment to the bug\n\u003e report -- that describes the policy, why the policy (closing outdated\n\u003e reports) exists, and how to avoid automated report closure.\n\nI can definitely do this, and give a wordy notice before I start the\ntimer. I will write up a message that links to a rebase walkthrough\n(any suggestions? I think Gavin has one somewhere...), I would like it\nto be more detailed than GitHub's walk-through.\n\nMy main reason for pushing this is that it will help clear out some of\nthe older pulls/issues that exist right now. I'm hoping that in the\nfuture, the QA process will be good enough that pulls/issues won't\nfall behind from lack of testing - and the timers will be used very\nsparingly. It should only be in place to sort out the pulls/issues\nthat the majority doesn't want included in the client.",
"sig": "50b1e597245410f388aa660126d923b2c1132d3f22a901a68799970c5e1a4e79dc42d4573a5f22adb7f8f33e197265b1684206fd1868895315552d1f59e8ff22"
}