Hi Jacek, thanks for catching this. That was my fault for not catching
this when creating the new RC.

I don't think it requires a new RC though as the CHANGELOG.md file
isn't currently being merged back to main after releases [1]. i.e.,
the mistake will only exist in git and in source tarballs for the
19.0.1 release. Happy to hear others' thoughts on not creating a new
RC though. Otherwise, let's continue with releasing RC1 once the vote
closes.

Thanks again for helping verify and catching the issue.

[1] https://github.com/apache/arrow/issues/15000

On Thu, Feb 13, 2025 at 10:02 AM Jacek Pliszka <jacek.plis...@gmail.com> wrote:
>
> Hi!
>
> Changelog entries for 19.0.1 are duplicated:
>
> https://github.com/apache/arrow/blob/272715f6df2a042d69881ffa03d5078c58e4b345/CHANGELOG.md
>
> Best Regards,
>
> Jacek
>
> czw., 13 lut 2025 o 15:54 Raúl Cumplido <rau...@apache.org> napisał(a):
> >
> > +1 (binding)
> >
> > I've run the following on Ubuntu 24.04:
> >
> > TEST_JS=0 TEST_INTEGRATION_JS=0 TEST_DEFAULT=0 TEST_SOURCE=1
> > ./dev/release/verify-release-candidate.sh 19.0.1 1
> > TEST_DEFAULT=0 TEST_APT=1 ./dev/release/verify-release-candidate.sh 19.0.1 1
> > TEST_DEFAULT=0 TEST_YUM=1 ./dev/release/verify-release-candidate.sh 19.0.1 1
> > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh 19.0.1
> > 1
> >
> > Kou, Bryce, thanks for the work on the release!
> >
> > Regards,
> > Raúl
> >
> > El jue, 13 feb 2025 a las 10:52, Gang Wu (<ust...@gmail.com>) escribió:
> >
> > > +1
> > >
> > > Verified the C++ build on my MacOS M1.
> > >
> > > Thanks!
> > >
> > > On Thu, Feb 13, 2025 at 2:12 PM Ruoxi Sun <zanmato1...@gmail.com> wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > On my M1 Mac, OS version Sonoma 14.7.1 (23H222), AppleClang
> > > > 15.0.0.15000309, verified cpp:
> > > >
> > > > TEST_DEFAULT=0 TEST_CPP=1 ./verify-release-candidate.sh 19.0.1 1
> > > >
> > > > *Regards,*
> > > > *Rossi SUN*
> > > >
> > > >
> > > > On Thu, Feb 13, 2025 at 10:25 AM Bryce Mecum <bryceme...@gmail.com>
> > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I would like to propose the following release candidate (RC1) of 
> > > > > Apache
> > > > > Arrow version 19.0.1. This is a release consisting of 12
> > > > > resolved GitHub issues[1].
> > > > >
> > > > > This release candidate is based on commit:
> > > > > 272715f6df2a042d69881ffa03d5078c58e4b345 [2]
> > > > >
> > > > > The source release rc1 is hosted at [3].
> > > > > The binary artifacts are hosted at [4][5][6][7][8][9].
> > > > > The changelog is located at [10].
> > > > >
> > > > > Please download, verify checksums and signatures, run the unit tests,
> > > > > and vote on the release. See [11] for how to validate a release
> > > > candidate.
> > > > >
> > > > > See also a verification result on GitHub pull request [12].
> > > > >
> > > > > The vote will be open for at least 72 hours.
> > > > >
> > > > > [ ] +1 Release this as Apache Arrow 19.0.1
> > > > > [ ] +0
> > > > > [ ] -1 Do not release this as Apache Arrow 19.0.1 because...
> > > > >
> > > > > [1]:
> > > > >
> > > >
> > > https://github.com/apache/arrow/issues?q=is%3Aissue+milestone%3A19.0.1+is%3Aclosed
> > > > > [2]:
> > > > >
> > > >
> > > https://github.com/apache/arrow/tree/272715f6df2a042d69881ffa03d5078c58e4b345
> > > > > [3]:
> > > > https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-19.0.1-rc1
> > > > > [4]: https://apache.jfrog.io/artifactory/arrow/almalinux-rc/
> > > > > [5]: https://apache.jfrog.io/artifactory/arrow/amazon-linux-rc/
> > > > > [6]: https://apache.jfrog.io/artifactory/arrow/centos-rc/
> > > > > [7]: https://apache.jfrog.io/artifactory/arrow/debian-rc/
> > > > > [8]: https://apache.jfrog.io/artifactory/arrow/python-rc/19.0.1-rc1
> > > > > [9]: https://apache.jfrog.io/artifactory/arrow/ubuntu-rc/
> > > > > [10]:
> > > > >
> > > >
> > > https://github.com/apache/arrow/blob/272715f6df2a042d69881ffa03d5078c58e4b345/CHANGELOG.md
> > > > > [11]:
> > > https://arrow.apache.org/docs/developers/release_verification.html
> > > > > [12]: https://github.com/apache/arrow/pull/45502
> > > > >
> > > >
> > >

Reply via email to