Yes, works like a charm now.

Author has reached the open pull request limit
is what I see now, when trying to move draft to Review.

Thanks Jan.

is
is

On Mon, Oct 26, 2026 at 5:33 AM Jan Høydahl <[email protected]> wrote:

> There was an error parsing our asf.yaml, fixed, please try again...
>
> Jan
>
> > 24. okt. 2026 kl. 23:42 skrev Jalaz Kumar <[email protected]>:
> >
> > Hi Jan
> >
> > Thanks for adding this cap, I can see that the PR is merged now. But I
> > don't think it's taking effect.
> > Out of curiosity, I tested this after the merge and I was able to open 7+
> > PRs since then without any block/warning.
> >
> > All 8 are still open, plus an older one. so, 9 are open in total. The cap
> > should have been at 7.
> >
> > Is there something more needed at ASF-Infra side for this to take effect,
> > or I may be missing something?
> >
> >
> > On Fri, Oct 16, 2026 at 8:14 PM Jan Høydahl <[email protected]> wrote:
> >
> >> https://github.com/apache/solr/pull/5163
> >>
> >>> 16. okt. 2026 kl. 16:31 skrev Jan Høydahl <[email protected]>:
> >>>
> >>> Hi,
> >>>
> >>> So far only positive feedback. Here's the PR, I'll merge on Monday...
> >>>
> >>> Jan
> >>>
> >>>> 15. okt. 2026 kl. 17:20 skrev Jan Høydahl <[email protected]>:
> >>>>
> >>>> Hello,
> >>>>
> >>>> The Apache Infrastructure team has recently introduced a configuration
> >> option that allows projects to set a maximum limit on concurrent pull
> >> requests from external contributors—those without write access—while
> >> exempting committers. Details are available at
> >>
> https://github.com/apache/infrastructure-asfyaml#pull-request-creation-cap
> >> .
> >>>>
> >>>> I propose implementing a cap across all Solr repositories. This
> >> adjustment would better align with our review capacity and encourage
> >> contributors to prioritize existing submissions.
> >>>>
> >>>> I suggest a threshold of seven as an initial estimate. A potential
> risk
> >> is that contributors might submit larger pull requests to maximize the
> >> limit, which could reduce reviewability; however, we can address this
> >> through feedback.
> >>>>
> >>>> This message is not a formal vote, and I do not anticipate one. If the
> >> discussion lacks consensus, becomes contentious, or encounters
> significant
> >> resistance, we may initiate a vote to resolve the matter.
> >>>>
> >>>> Jan
> >>>
> >>
> >>
> >
> > --
> > Regards
> > Jalaz Kumar
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

-- 
Regards
Jalaz Kumar

Reply via email to