Re: [Numpy-discussion] Numpy pull requests getting out of hand.

2016-02-01 Thread Evgeni Burovski
On Mon, Feb 1, 2016 at 11:22 PM, Julian Taylor wrote: > I don't like that approach, closing PRs with valuable code causes them > to get lost in the much larger set of closed ones. > Instead we could tag them appropriately so they can be found by > parties interested in using or finishing them. The

Re: [Numpy-discussion] Numpy pull requests getting out of hand.

2016-02-01 Thread Julian Taylor
I don't like that approach, closing PRs with valuable code causes them to get lost in the much larger set of closed ones. Instead we could tag them appropriately so they can be found by parties interested in using or finishing them. These could also be used for new contributors to work on. You coul

Re: [Numpy-discussion] Numpy pull requests getting out of hand.

2016-01-31 Thread Jeff Reback
FYI also useful to simply close by time - say older than 6 months with a message for the writer to reopen if they want to work on it then u don't get too many stale ones my 2c > On Jan 31, 2016, at 2:10 PM, Charles R Harris > wrote: > > Hi All, > > There are now 130 open numpy pull request

[Numpy-discussion] Numpy pull requests getting out of hand.

2016-01-31 Thread Charles R Harris
Hi All, There are now 130 open numpy pull requests and it seems almost impossible to keep that number down. My personal decision is that I am going to ignore any new enhancements for the next couple of months and only merge bug fixes, tests, house keeping (style, docs, deprecations), and old PRs.