Hi Ivan, Unfortunately, I don't have the necessary rights to close PRs. Only PR author can close.
I can only imagine the following way: Produce fake commit(s) with message Fixes #NNNN. But this may be acceptable if PR author is not responding. Simple expiration policy may have its own issues. There can be - an enthusiast who didn't provide correctly set up ticket - But prepared just PR with a good addition to the product. It is not so correct to accept such contribution (HTC requires JIRA), but anyway, having PR open we can ask him or her to set up a ticket. Sincerely, Dmitriy Pavlov вт, 11 дек. 2018 г. в 09:24, Pavel Tupitsyn <ptupit...@apache.org>: > Agree with Dmitriy. > > We use GitHub PRs in our workflow, therefore we should keep them in order. > > We can close PRs that refer to closed tickets, this can be done with a > simple script. > > On Tue, Dec 11, 2018 at 9:15 AM Павлухин Иван <vololo...@gmail.com> wrote: > > > Nikolay, > > > > I must say that when I first saw 1K+ open PRs my first thought was > > that something was wrong with a review process. In my mind in not very > > big project open PR list can reflect very well the real work in > > progress. For bigger projects things become more complicated. > > > > Dmitriy, > > > > Do you have some cleanup automation in mind? Immediately I think that > > it is fully safe to close all PRs that were not touched more than a > > year. > > пн, 10 дек. 2018 г. в 20:01, Dmitriy Pavlov <dpav...@apache.org>: > > > > > > The main concern is related to chances that newcomer will have to > obtain > > a > > > review support from the community. > > > > > > Actually, a lot of people doing their best to provide a feedback to > > > newcomers, and count of issues still in PA state goes down (84 is a > > > relatively small count of issues in PA state). But 1428 PRs may imply > we > > > don't review here, as we have tons of incomplete PRs. Actually, most of > > > these PRs were merged (but not using ./apply-pull-request.sh script, > but > > > manually, without reference to PRs). > > > > > > Another benefit of revising this list, if there are any changes which > > > were not accomplished with a proper ticket with PA status, we will > > identify > > > a number of additional contributions to be applied to the codebase. > > > > > > > > > пн, 10 дек. 2018 г. в 19:53, Nikolay Izhikov <nizhi...@apache.org>: > > > > > > > Hello, Dmitriy. > > > > > > > > What, exactly concerns newcomers? > > > > What is wrong with opened PR? > > > > How project will benefit from closed PR? > > > > > > > > > The same proposal is related to IEP statuses. If you were involved > > in an > > > > IEP, please validate its status > > > > > > > > +1. We should maintain IEP description up to date. > > > > > > > > пн, 10 дек. 2018 г., 19:15 Dmitriy Pavlov dpav...@apache.org: > > > > > > > > > Hi Igniters, > > > > > > > > > > Newcomers to Apache Ignite sometimes became concerned about many > > open PRs > > > > > in the project. Apache Ignite TC Bot also performs runs checks with > > a PR > > > > > open. Apache Ignite pulls list > > https://github.com/apache/ignite/pulls > > > > > contains > > > > > 1442 PRs open while only 84 issues are waiting for review. > > > > > > > > > > Could you please verify the list of your PRs in Apache Ignite > > > > > https://github.com/pulls and close every not needed/already > merged > > > > > change? > > > > > > > > > > The same proposal is related to IEP statuses. If you were involved > > in an > > > > > IEP, please validate its status here > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Active+Proposals > > > > > Please > > > > > set a correct state for your IEP, as well. > > > > > > > > > > Should you have any questions, please don't hesitate to ask here. > > Thank > > > > you > > > > > in advance! > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > >
