Py4J 0.11 release prep: version bump + complete changelog - #18
Open
Tagar wants to merge 2 commits into
Open
Conversation
Bump version 0.10.9.9 -> 0.11 across the 5 release-controlled files (ant.properties, gradle.properties, pom.xml, build.gradle POM block, version.py) and rewrite the changelog into a complete 0.11 entry. The prior 'Unreleased' section listed only 3 of ~15 notable changes; enumerated all 26 commits since the 0.10.9.9 tag. Breaking changes first: Python 2 removal (py4j#585), attribute-cache identity shift (py4j#596), decode_bytearray (py4j#593), cold-start (py4j#595), TCP_NODELAY (py4j#592), Py3 modernization (py4j#594), fixes (py4j#499, py4j#554), listener-lifecycle + graceful-shutdown, perf-framework / CodSpeed / CI work. Release date and milestone link left as TBD; index.rst news line deferred to publish time. Version floor verified as Python >=3.9. Co-authored-by: Isaac <no-reply@databricks.com>
…wn PR ref Two fixes from the fan-out audit of PR #18: - index.rst: add the 0.11 news entry (date TBD) — every release commit since 0.10.9.7 has added one; ours was missing it. - changelog: add (py4j#582) to the graceful-shutdown bullet, the only feature that lacked a PR reference. Deferred to publish time: the 'tickets closed for 0.11' milestone link (needs the GitHub milestone created first) and the real release date. Co-authored-by: Isaac <no-reply@databricks.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Py4J 0.11 release preparation
Bumps the version to
0.11across all release-controlled files and writes thecomplete
0.11changelog. byteoak testing PR — validates the build/CI at0.11before any upstream release.Why
0.11(not0.10.9.10)The
0.10.9.Nscheme was versioning inertia — features (Java 11/17, Python3.10/3.11/3.12 support) shipped under a frozen
0.10.9. This is the firstrelease since
0.10.9.9(Jan 2025) and it carries genuine minor-level change(Python 2 removal, a behavior-changing attribute cache, perf work), so it moves
to
0.11. Matches the historical 2-part minor tags (0.9,0.10).Version bump (5 files, per
release_process.mdstep 0)py4j-java/ant.propertiespy4j-java/gradle.properties(bundleVersion+version)py4j-java/pom.xmlpy4j-java/build.gradle(Maven POM block)py4j-python/src/py4j/version.pyChangelog
The old "Unreleased" section listed only 3 of ~15 notable changes. Rewrote it as
a complete
0.11entry from all 26 commits since the0.10.9.9tag, breakingchanges first: Python 2 removal (py4j#585), attribute-cache + identity shift
(py4j#596), decode_bytearray (py4j#593), cold-start (py4j#595), TCP_NODELAY (py4j#592), Py3
modernization (py4j#594), fixes (py4j#499, py4j#554), listener-lifecycle + graceful-shutdown,
and the perf-framework / CodSpeed / CI work.
Deliberately deferred (not in this PR)
TBD) and thetickets closedmilestone link — set at publish.index.rstnews line — added at publish with the real date.release.yml) — separate PR.Left intentionally at
0.10.9.9Perf baselines, mock test fixtures, and the old news line — historical records.
Verified: no test couples to the version string; Python floor is
>=3.9.