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

   ## Which issue does this PR close?
   
   There is no issue for this. It follows up #6282 and uses the generator from 
#6358.
   
   ## Rationale for this change
   
   The 1.1.0 changelog merged in #6282 was generated before #6358, so it 
credits each PR only to the author of its merge commit. That leaves Michael 
Taranov (`mixermt`) out of the changelog entirely, although #6219 carries the 
commits from their #6092, and it credits the four backports only to the person 
who opened them, not to the authors of the original changes.
   
   ## What changes are included in this PR?
   
   `docs/source/changelog/1.1.0.md`, regenerated with the generator from #6358 
for the same range as #6282 (`1.0.0..021c378fc`, the branch before #6282 
itself) and formatted with prettier 3.9.9. Compared with the current file:
   
   - #6219 is credited to `andygrove, mixermt`, #6223 to `andygrove, 
snmvaughan` and #5310 to `manuzhang, andygrove`, and the backports #6266, 
#6305, #6318 and #6323 also credit `dwsmith1983`, `liupoyi-1031` and 
`parthchandra`.
   - The credits add Michael Taranov and count each co-authored PR for Andy 
Grove, dustin, Parth Chandra, Steve Vaughan and liupoyi-1031. The header says 
41 contributors instead of 40.
   - The credits sentence says that a PR with commits from more than one person 
counts for each of them.
   
   Nothing else changed, so no PR titles or labels have moved since #6282 was 
generated. #6307 and the #6312 backport are not on the branch yet. If they land 
before the RC, the changelog needs regenerating again, with the #6358 
generator, since `branch-1.1` still has the old one.
   
   ## How are these changes tested?
   
   The generator's before and after comparison on this release is in #6358. 
Here, `prettier --check` passes on the changed file, and 
`dev/ci/compute-changes.py` selects none of the test suites for it.
   


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