andygrove opened a new pull request, #89:
URL: https://github.com/apache/datafusion-java/pull/89

   ## Which issue does this PR close?
   
   - No tracking issue. Release-prep PR against \`branch-0.1\`.
   
   ## Rationale for this change
   
   \`branch-0.1\` is the release branch for the 0.1.0 line. Before cutting the 
first RC tag we need (a) a written changelog covering everything that landed 
since the project was seeded, and (b) the version stripped of its \`-SNAPSHOT\` 
suffix so the published artifact's coordinates match the release tag.
   
   ## What changes are included in this PR?
   
   - **\`dev/changelog/0.1.0.md\`** (new) — generated by 
\`dev/release/generate-changelog.py\` from PR #88, walking the range from the 
root commit (\`68bcdb6\` \"Create README.md\") to the current \`branch-0.1\` 
HEAD (\`76a5454\`). 48 commits from 2 contributors, categorized as:
     - 1 breaking change (\`!:\` Conventional Commit)
     - 1 bug fix
     - 27 enhancements (\`feat:\`)
     - 5 documentation updates
     - 9 other (release tooling, CI, build, refactoring)
     - Plus a credits block with per-contributor commit counts.
   - **\`pom.xml\`, \`core/pom.xml\`, \`examples/pom.xml\`** — bump 
\`<version>\` from \`0.1.0-SNAPSHOT\` to \`0.1.0\` (one line in each — the 
parent declaration, with the two child modules inheriting via \`<parent>\`).
   
   The native crate version in \`native/Cargo.toml\` is already at \`0.1.0\`, 
so no change there.
   
   ## Are these changes tested?
   
   \`./mvnw -q validate\` is clean on the rewritten poms (parent + both 
children resolve to a consistent \`0.1.0\` version).
   
   \`dev/release/generate-changelog.py\` was end-to-end tested against the same 
range during the development of PR #88 (smoke-tested in that PR's description 
against \`HEAD~3..HEAD\`); the full \`branch-0.1\` run produced the file in 
this PR with no manual edits.
   
   This PR depends on PR #88 (which adds the generator) only at run-time — the 
output (\`dev/changelog/0.1.0.md\`) is what ships here, not the generator 
itself. PR #88 is targeted at \`main\`; this PR is targeted at \`branch-0.1\`. 
They can land in either order.
   
   ## Are there any user-facing changes?
   
   The published artifact coordinates change from 
\`org.apache.datafusion:datafusion-java:0.1.0-SNAPSHOT\` to 
\`org.apache.datafusion:datafusion-java:0.1.0\`. This is the intended effect of 
the release.


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to