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

   Draft of the Apache DataFusion Comet 1.2.0 release post. Tracking issue: 
apache/datafusion-comet#6889. Release tracking: apache/datafusion-comet#6550. 
The change log it links to is in apache/datafusion-comet#7168.
   
   The theme is results that match Spark (timezones, floats, collations, 
wrong-results fixes), followed by memory/shuffle, Iceberg, and the new 
integrations (Delta Lake and Python UDFs, both experimental).
   
   Open items before this is ready to publish:
   
   - **Date and file name.** `2026-11-03` is a placeholder. Rename the file to 
the real publish date.
   - **Commit and contributor counts.** The post uses the counts from the 
generated change log (388 commits, 40 contributors). That command compares 
against the `1.1.0` tag, so it also counts the `main` originals of fixes that 
shipped in 1.1.0 as backports. Matching them out gives about 336 new commits on 
`main` as of 2026-10-23. Decide which to quote, and refresh when the change log 
is regenerated.
   - **Performance figures** are quoted from PR descriptions and have not been 
re-measured: #7059, #6943, #7065, #7016, #6698, #6937, #7094, #5496, #6350, 
#5130, #6130.
   - **Branch-1.2 links** (change log, installation guide) need the branch and 
docs to exist at publish time.
   - **Scope check.** The post says native Iceberg writes and the in-memory 
cache stay opt-in, and that the Iceberg default is revisited after the branch 
is cut. Adjust if the plan changes before the release.
   - **Credits.** Handles come from the PR authors. Reviewers are not credited 
yet, unlike the 1.1.0 post.
   


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