Hi,

> When you say prepare I suppose we will only have to re-upload binaries and
> then send a new vote, right?

Right.

> I am happy to accommodate whatever works best here. Maybe we should just
> continue with Arrow 16.1.0 RC1 only because the repositories have been
> overwritten with those at the moment. So we can continue with the Arrow
> vote and we can push ADBC once we finish.
> 
> Just had a chat with David and he's ok with that approach.

OK. Let's choose that approach.


Thanks,
-- 
kou

In <CAGvDy=rE_8181r1sgHQ8WD=ut5y_gFa8vjwGdAJr8PE=gy0...@mail.gmail.com>
  "Re: [VOTE] Release Apache Arrow ADBC 12 - RC3" on Thu, 9 May 2024 15:21:15 
+0200,
  Raul Cumplido Dominguez <r...@voltrondata.com.INVALID> wrote:

> Hi Kou,
> 
> Sorry about that, I was not aware of the issue.
> 
> When you say prepare I suppose we will only have to re-upload binaries and
> then send a new vote, right?
> 
> I am happy to accommodate whatever works best here. Maybe we should just
> continue with Arrow 16.1.0 RC1 only because the repositories have been
> overwritten with those at the moment. So we can continue with the Arrow
> vote and we can push ADBC once we finish.
> 
> Just had a chat with David and he's ok with that approach.
> 
> Kind regards,
> Raúl
> 
> On Thu, May 9, 2024 at 2:56 PM Sutou Kouhei <k...@clear-code.com> wrote:
> 
>> Hi David and Raúl,
>>
>> Sorry. The current release process of APT/Yum repositories
>> doesn't allow multiple releases in parallel. In this case,
>> the following timeline isn't allowed:
>>
>> 1. Prepare ADBC 12 RC3
>> 2. Prepare Arrow 16.1.0 RC1
>> 3. Release ADBC 12
>> 4. Release Arrow 16.1.0
>>
>> We have only one APT/Yum repositories for RC. So APT/Yum
>> repositories for 1. was overwritten by APT/Yum repositories
>> for 2.
>>
>> Can we use the following timeline?
>>
>> 1. Prepare Arrow 16.1.0 RC1
>> 2. Release Arrow 16.1.0
>> 3. Prepare ADBC 12 RC3
>> 4. Release ADBC 12
>>
>> Or:
>>
>> 1. Prepare ADBC 12 RC3
>> 2. Release ADBC 12
>> 3. Prepare Arrow 16.1.0 RC1
>> 4. Release Arrow 16.1.0
>>
>>
>> Thanks,
>> --
>> kou
>>
>> In <face88c8-8b1e-432b-9d86-e19368d21...@app.fastmail.com>
>>   "[VOTE] Release Apache Arrow ADBC 12 - RC3" on Thu, 09 May 2024 15:54:09
>> +0900,
>>   "David Li" <lidav...@apache.org> wrote:
>>
>> > Hello,
>> >
>> > I would like to propose the following release candidate (RC3) of Apache
>> Arrow ADBC version 12. This is a release consisting of 56 resolved GitHub
>> issues [1].
>> >
>> > Please note that the versioning scheme has changed.  This is the 12th
>> release of ADBC, and so is called version "12".  The subcomponents,
>> however, are versioned independently:
>> >
>> > - C/C++/GLib/Go/Python/Ruby: 1.0.0
>> > - C#: 0.12.0
>> > - Java: 0.12.0
>> > - R: 0.12.0
>> > - Rust: 0.12.0
>> >
>> > These are the versions you will see in the source and in actual
>> packages.  The next release will be "13", and the subcomponents will
>> increment their versions independently (to either 1.1.0, 0.13.0, or
>> 1.0.0).  At this point, there is no plan to release subcomponents
>> independently from the project as a whole.
>> >
>> > Please note that there is a known issue when using the Flight SQL and
>> Snowflake drivers at the same time on x86_64 macOS [12].
>> >
>> > This release candidate is based on commit:
>> 91804736a5c478fcd9a69930c4bbef8f7af90a7f [2]
>> >
>> > The source release rc3 is hosted at [3].
>> > The binary artifacts are hosted at [4][5][6][7][8].
>> > The changelog is located at [9].
>> >
>> > Please download, verify checksums and signatures, run the unit tests,
>> and vote on the release. See [10] for how to validate a release candidate.
>> Please use the latest version of the verification script on 'main', and not
>> the verification script in the source tarball.
>> >
>> > See also a verification result on GitHub Actions [11].
>> >
>> > The vote will be open for at least 72 hours.
>> >
>> > [ ] +1 Release this as Apache Arrow ADBC 12
>> > [ ] +0
>> > [ ] -1 Do not release this as Apache Arrow ADBC 12 because...
>> >
>> > Note: to verify APT/YUM packages on macOS/AArch64, you must `export
>> DOCKER_DEFAULT_PLATFORM=linux/amd64`. (Or skip this step by `export
>> TEST_APT=0 TEST_YUM=0`.)
>> >
>> > [1]:
>> https://github.com/apache/arrow-adbc/issues?q=is%3Aissue+milestone%3A%22ADBC+Libraries+12%22+is%3Aclosed
>> > [2]:
>> https://github.com/apache/arrow-adbc/commit/91804736a5c478fcd9a69930c4bbef8f7af90a7f
>> > [3]:
>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-adbc-12-rc3/
>> > [4]: https://apache.jfrog.io/artifactory/arrow/almalinux-rc/
>> > [5]: https://apache.jfrog.io/artifactory/arrow/debian-rc/
>> > [6]: https://apache.jfrog.io/artifactory/arrow/ubuntu-rc/
>> > [7]:
>> https://repository.apache.org/content/repositories/staging/org/apache/arrow/adbc/
>> > [8]:
>> https://github.com/apache/arrow-adbc/releases/tag/apache-arrow-adbc-12-rc3
>> > [9]:
>> https://github.com/apache/arrow-adbc/blob/apache-arrow-adbc-12-rc3/CHANGELOG.md
>> > [10]:
>> https://arrow.apache.org/adbc/main/development/releasing.html#how-to-verify-release-candidates
>> > [11]: https://github.com/apache/arrow-adbc/actions/runs/9013195701
>> > [12]: https://github.com/apache/arrow-adbc/issues/1841
>>

Reply via email to