SEZ9 commented on issue #10753: URL: https://github.com/apache/seatunnel/issues/10753#issuecomment-5476201601
Thanks @goutamadwant for the thorough status pass — this is exactly the kind of housekeeping this tracker needs, especially since assignees can't edit the issue description themselves. Responding to your points: 1. **Azure Queue Storage Source** — extending the existing sink connector module and reusing its authentication and message configuration is the right approach. Go ahead; consider the slice yours. 2. **Stale assignments** — agreed that claims with no PR and no activity for 60+ days should be reconfirmed before they keep blocking others. Thanks for pinging those contributors directly. Let's give them two weeks from your ping to respond; if there's no reply by then, we'll release those slices for new claimants. 3. **Aging but within 60 days** — I'll leave those as assigned for now, but a short status comment from the contributors on their open PRs would help us plan. 4. **Tracker refresh** — I'll update the issue description to mark the completed slices as done and reflect the active work exactly as you've laid it out. Concrete remaining asks: - If any of the stale assignees reply to your ping, please drop a note here so the tracker stays current. - For the GCS Sink work stacked on your fork, please open it against the apache repo once the GCS Source lands so we can track it in this issue. - Keep including last-activity dates in future status passes — it makes triage much easier. Thanks again for driving this forward. <!-- streview-comment:688 --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
