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

[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 could also tag and close them, but I find it makes them harder to
discover especially for outsiders who are not aware of this policy.

Also we could extend our contribution guidelines to note that
reviewing existing PRs can be a much more valuable contribution than
adding new code. Possibly adding some review guidelines.


On 31.01.2016 20:25, Jeff Reback wrote:
> 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 <charlesr.harris at gmail.com> wrote:
>>
>> 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. I would also request that other maintainers start looking a taking care of older PRs, either cleaning them up and merging, or closing them.
>>
>> Chuck
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion at scipy.org
>> https://mail.scipy.org/mailman/listinfo/numpy-discussion
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>