On Mon, Sep 19, 2011 at 8:20 PM, Alex Waters <ampe...@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 > q...@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. jgar...@exmulti.com ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
