DanielLeens commented on issue #10753:
URL: https://github.com/apache/seatunnel/issues/10753#issuecomment-6109277785

   Tracking refresh — checked on 2026-10-11 against this thread, the linked 
PRs, and current `dev`.
   
   **Done in `dev`**
   
   - Azure Event Hubs Source: #12048 merged on 2026-09-29.
   - ActiveMQ Classic Source: #12341 merged on 2026-10-09. This completes the 
narrow ActiveMQ Classic source slice only; the generic JMS/AMQP request remains 
a separate tracker item.
   - Sentry project error-events Source: #12451 merged on 2026-10-11.
   
   **Active, and not available for a duplicate claim**
   
   - WooCommerce orders Source: #12450 remains open with changes requested and 
a blocked merge state. Its latest recorded Build is successful, but the 
remaining review/maintainer discussion must be resolved on that PR before it 
can move to Done.
   - Asana Source: #12712 is the dedicated feature issue and #12719 is now the 
implementation PR. The PR is still a draft, has requested changes, and its 
latest Build failed, so it remains In progress rather than ready for review or 
merge. Please keep the technical follow-up on #12712 / #12719.
   - BigQuery Source: @chovy-3012 has the current declared intent. `dev` 
contains the existing BigQuery sink module but no merged BigQuery Source 
implementation, and there is still no linked source PR. Please avoid parallel 
work until that proposal/PR is clarified.
   
   **Older open PR paths remain reserved**
   
   The tracker rows backed by #11902 (ABFS), #12293 (ADLS), #10986 (Azure Data 
Explorer), #10447 (HubSpot), #11838 (Splunk Sink), and #10900 (Syslog Source) 
are still open. They should be continued or explicitly relinquished on their 
own PRs, not silently duplicated here.
   
   No labels, assignments, or issue state were changed by this tracking refresh.


-- 
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]

Reply via email to