From: Alex Waters <ampedal@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Issue / Pulls timers
Date: Tue, 20 Sep 2011 22:34:35 -0400 [thread overview]
Message-ID: <CAL0fb60XRvgSxL6OPQ0r_tK5RvCny_B8ECU7VCk8D9RJcU3Q2w@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpdF88tTHOT40=-9enrb4hsekexELSrctdHDK8QqWxGVXw@mail.gmail.com>
> 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.
prev parent reply other threads:[~2011-09-21 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 0:20 Alex Waters
2011-09-20 18:54 ` Jeff Garzik
2011-09-21 2:34 ` Alex Waters [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL0fb60XRvgSxL6OPQ0r_tK5RvCny_B8ECU7VCk8D9RJcU3Q2w@mail.gmail.com \
--to=ampedal@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox