Prepare 2.17.0a0.

[stuhood]

No description provided.

[stuhood]

Internal

• Remove unecessary checkout from the welcome action (#19037)

• Remove CODEOWNERS (#19024)

• Add a new GitHub Action to greet newcomers (#18977)

• Fixes for release job (#19033)

• Remove superfluous space from cherry pick script (#19030)

• Fix cherry pick reviewer list (#19029)

• Add missing space in cherry_pick.sh (#19026)

• Use correct secrets name in auto-cherry-picker (#19025)

• Add an auto-cherry-pick GitHub Action (#19021)

• Port Address to Rust (#18989)

• Move disabling the native-client into the native client itself (#19010)

• Add Python tomllib module to the list of known stdlib modules to be unowned (#19005)

• Prepare 2.15.1rc3. (#18997)

• Prepare 2.14.2. (#18996)

• Replace Snapshot::_unsafe_create with create_for_testing. (#18995)

• Prepare the 2.16.0rc2 release. (#18986)

• Tweak the cherry-pick script (#18988)

• Move mandatory process' level to DEBUG (#18982)

• Log new dependency parsing at Debug, not Info (#18976)

• Have the cherry-pick script do every relevant milestone (#18975)

• Bump pyo3-build-config from 0.17.2 to 0.18.3 in /src/rust/engine (#18767)

• Bump Pyo3 to 0.18 (#18968)

• DRY Lambda/GCF FaaS targets (#18964)

• Handle comment as first entry after try: (#18962)

• CODEOWNERS: add @kaos to a few places. (#18967)

• Add initial CODEOWNERS with me (#18953)

• Have this repo use the new rust parser for Python (#18954)

• Add module mappings for all OTEL instrumentation libraries (#18945)

[kaos]

Oh, I've been sleeping on #17671

I'll want to pick that one to 2.16.1, thought I'd get it into 2.17 :p

[stuhood]

I'll want to pick that one to 2.16.1, thought I'd get it into 2.17 :p

Picking to 2.17.x should be very viable as long as you do it before we switch to rcs. But it's questionable for 2.16.x I think...

[kaos]

I'll want to pick that one to 2.16.1, thought I'd get it into 2.17 :p

Picking to 2.17.x should be very viable as long as you do it before we switch to rcs. But it's questionable for 2.16.x I think...

That's why I indicated 2.16.1, leaning on the release strategy:

Any new patch versions will only include:

Backward-compatible bug fixes
Backward-compatible feature backports, as long as they:

• Are requested by users
• Are deemed low-risk and are easy to backport
• Do not introduce new deprecations

[stuhood]

Touché! I forgot that we had included that. Yea, seems fine.