Not at all.. But sometimes a PR might need a little bit of "encouragement" to get over the finish line.
And I've had PRs that have gotten a little bit "old", if you will.. Usually a simple message to the group that I've rebased the code, tested it out again against the latest code base, and it is ready to go, will do the trick. -brad w. On Thu, Dec 1, 2022 at 6:01 AM Łukasz Bownik <lukasz.bow...@gmail.com> wrote: > " The slowest response times are for issues where the submitter has gone > silent and the pull response might need a little bit of work." > > Does it mean non-critical PRs get starved unless the submitter is annoying? > > On Tue, Nov 29, 2022 at 8:41 PM Neil C Smith <neilcsm...@apache.org> > wrote: > > > On Tue, 29 Nov 2022 at 19:16, Eric Bresie <ebre...@gmail.com> wrote: > > > Others need to be identified and coordinated for inclusion in a give > > release with release manager . > > > > That only applies to PRs targeting delivery or release** branches, > > which tend to be managed a little differently. Also, release team, > > not single release manager. > > > > Neil > >
