Abacn opened a new pull request, #39899:
URL: https://github.com/apache/beam/pull/39899

   * Update overall roadmap highlights:
     - Add section for Extended Metadata and SDK-level CDC support
     - Highlight SchemaTransform API, Beam YAML, and Managed I/O under 
cross-language transforms
     - Update supported runtime versions for Python (3.10-3.14) and Java (11, 
17, 21, 25)
   
   * Modernize SDK connector roadmaps:
     - Java: Add Extended Metadata/CDC, OpenTelemetry trace context propagation 
(#33176), and lakehouse format ecosystem (Iceberg, Delta Lake, Managed I/O); 
remove stale connector items
     - Python: Reframe around Java cross-language SchemaTransforms, 
auto-generated transform wrappers, and native Beam ML / AI ecosystem
     - Go: Add portable schemas/logical types (#39684), auto cross-language 
wrappers, native utility transforms (GroupIntoBatches, Watch), and first-class 
I/Os
     - Multi-SDK: Mark legacy roadmap as stale
   
   * Refresh runner roadmaps:
     - Flink: Document Flink 2.x support and DataStream API batch migration
     - Spark: Transition from Spark 3 to Spark 4 and Structured Streaming 
improvements
     - Dataflow & Prism: Update GitHub issue tracker links and resources
   
   * Mark Euphoria DSL as deprecated and scheduled for removal
   
   **Please** add a meaningful description for your change here
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable. This will automatically add a link to the 
pull request in the issue. If you would like the issue to automatically close 
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/actions/workflows/build_wheels.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/actions/workflows/python_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/actions/workflows/java_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Go 
tests](https://github.com/apache/beam/actions/workflows/go_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI or the [workflows 
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) 
to see a list of phrases to trigger workflows.
   


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