What's the timeframe for getting a source contribution reviewed? (https://github.com/airbytehq/airbyte/pull/67023) Tests completed and passed, ready to go...but is it likely to be 1 week, a month, many months? I want to resist switching to the local forked build but business needs for the new stream will only get louder

We have a two-week target for community contributions, but we're trending well below that, usually a week or less in most cases. The team has been pretty on top of them. Shouldn't be long!

Perfect, thank you!

I'll ping the team about it but I suspect it just still needs 👍 from an engineer. Sorry for the delay.

Thanks! Yes looks like a reviewer just needs to hit approve

I'm in the same boat (https://github.com/airbytehq/airbyte/pull/66728): going on three weeks, fixes an issue, all test passing. Anything we can do to help as members of the community to help streamline, assist, or help provide reviews?

Sorry for the delay. I talked with the engineer and he's aware. Looks like there's a bit of a backlog on submissions recently. He's moving through each PR in the queue and will hopefully finalize these shortly. I can see them on the team's board so it shouldn't be too much longer. If he needs anything he'll comment on the PR. However, nothing else is needed from either of you right now. Thanks again for your patience.

@Ian Alton any chance on moving forward with PR 66728 (Resolves 66727)? Maybe it got tagged wrong somehow?

I'll ping the eng. team about it again