From: Alex Waters <ampedal@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Issue / Pulls timers
Date: Mon, 19 Sep 2011 20:20:19 -0400 [thread overview]
Message-ID: <CAL0fb63-zObvzirU1T6-xQnKc4=Ly2go5BBF9Q0XjqAc3o8V7A@mail.gmail.com> (raw)
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@BitcoinTesting•org. "
This will help cut down on the abandoned / stagnant pulls and issues.
It will also focus attention on priority items, and phase out unwanted changes.
Sidenote: QA@BitcoinTesting•org is working, unlike QA@Bitcoin•org
-Alex
next reply other threads:[~2011-09-20 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 0:20 Alex Waters [this message]
2011-09-20 18:54 ` Jeff Garzik
2011-09-21 2:34 ` Alex Waters
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='CAL0fb63-zObvzirU1T6-xQnKc4=Ly2go5BBF9Q0XjqAc3o8V7A@mail.gmail.com' \
--to=ampedal@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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