Hm, I can see 28fc91a2a5a8ede5797fde04527f76f351c3cd8b as the latest.

git log upstream/branch-53
commit 28fc91a2a5a8ede5797fde04527f76f351c3cd8b (HEAD -> b53, 
upstream/branch-53, origin/b53)

Not sure why the script took earlier commit. I'll recreate the tarball and 
create another voting thread

On 2026/03/16 16:18:51 Tim Saucer wrote:
> -1 (binding)
> 
> I think the commit generated in the script here is not what we want. I
> think we want the latest on the branch
> at 28fc91a2a5a8ede5797fde04527f76f351c3cd8b.
> 
> When I tried running the commit above I'm getting quite a few things
> missing.
> 
> Best,
> Tim
> 
> On Mon, Mar 16, 2026 at 11:43 AM <[email protected]> wrote:
> 
> > Hi,
> > I would like to propose a release of Apache DataFusion version 53.0.0.
> > This release candidate is based on commit:
> > 23e7a19186e71044a610e5bfcc4e647598bf557a [1]
> > The proposed release tarball and signatures are hosted at [2].
> > The changelog is located at [3].
> > Please download, verify checksums and signatures, run the unit tests, and
> > vote
> > on the release. The vote will be open for at least 72 hours.
> > Only votes from PMC members are binding, but all members of the community
> > are
> > encouraged to test the release and vote with "(non-binding)".
> > The standard verification procedure is documented at
> > https://github.com/apache/datafusion/blob/main/dev/release/README.md#verifying-release-candidates
> > .
> > [ ] +1 Release this as Apache DataFusion 53.0.0
> > [ ] +0
> > [ ] -1 Do not release this as Apache DataFusion 53.0.0 because...
> > Here is my vote:
> > +1
> > [1]:
> > https://github.com/apache/datafusion/tree/23e7a19186e71044a610e5bfcc4e647598bf557a
> > [2]:
> > https://dist.apache.org/repos/dist/dev/datafusion/apache-datafusion-53.0.0-rc1
> > [3]:
> > https://github.com/apache/datafusion/blob/23e7a19186e71044a610e5bfcc4e647598bf557a/CHANGELOG.md
> >
> 

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

Reply via email to