I have an open PR that's been reviewed but keeps getting dropped. Specifically, I've had to make a comment asking for updates on the PR's status 3 times, with the last comment going ignored. I'm not upset, since I understand that the team is very busy (I actually looked through the archives a while ago and saw that NumPy 2.0 is in development, which must be taking up a lot of your time), but I'm sure you also understand that I don't want my PR to hang in limbo forever. If the team doesn't have time to deal with it now, it should at least be given a triage tag so it's properly labelled and put on the backburner. Best regards, Matteo. P.S. I originally tried to send this message as an email, but it was instantly rejected because I'm not a list member. That's a pretty serious error for a public mailing list.
On Sat, Mar 25, 2023 at 12:35 PM Matteo Raso via NumPy-Discussion <numpy-discussion@python.org> wrote:
That's very normal on a mailing list. Even if you disagree with the design, the immediate failure message was very clear so you know how to fix it (sign up first, then resend your message). And the URL to the issue in question, certainly not a trivial issue where a quick review and resolution might be expected: https://github.com/numpy/numpy/pull/23061 Peter
Hello, Matteo Indeed, it is fairly standard practice for mailing lists to require subscription before posting, that's how we stop spam. Thank you for you contributions and for your message. We understand how frustrating it can be to submit your contribution and wait for it to be reviewed and merged. All of us, contributors and maintainers, have gone through this multiple times with our prs as well. Like most open source projects, we operate on limited resources and need to make very hard decisions with the little time we have to make the best we can. In addition, we all take NumPy very seriously, meaning that sometimes maintainers need a little extra time to make sure we have the right fix that will not create problems downstream or break things. This means sometimes reviews take longer than we would like. We appreciate your patience in this matter, and hope you are understanding. Sincerely, Melissa On Sat, Mar 25, 2023 at 9:32 AM Matteo Raso via NumPy-Discussion < numpy-discussion@python.org> wrote:
On Sat, Mar 25, 2023 at 12:35 PM Matteo Raso via NumPy-Discussion <numpy-discussion@python.org> wrote:
That's very normal on a mailing list. Even if you disagree with the design, the immediate failure message was very clear so you know how to fix it (sign up first, then resend your message). And the URL to the issue in question, certainly not a trivial issue where a quick review and resolution might be expected: https://github.com/numpy/numpy/pull/23061 Peter
Hello, Matteo Indeed, it is fairly standard practice for mailing lists to require subscription before posting, that's how we stop spam. Thank you for you contributions and for your message. We understand how frustrating it can be to submit your contribution and wait for it to be reviewed and merged. All of us, contributors and maintainers, have gone through this multiple times with our prs as well. Like most open source projects, we operate on limited resources and need to make very hard decisions with the little time we have to make the best we can. In addition, we all take NumPy very seriously, meaning that sometimes maintainers need a little extra time to make sure we have the right fix that will not create problems downstream or break things. This means sometimes reviews take longer than we would like. We appreciate your patience in this matter, and hope you are understanding. Sincerely, Melissa On Sat, Mar 25, 2023 at 9:32 AM Matteo Raso via NumPy-Discussion < numpy-discussion@python.org> wrote:
participants (3)
-
Matteo Raso -
Melissa Mendonça -
Peter Cock