I'll update MSYS2 package:
1. [done] rebase master
2. [done] upload source
3. [done] upload binaries
4. [done/PR-ready] update website
5. [done] upload ruby gems
6. [ ] upload js packages
8. [done] upload C# packages
9. [andygrove] upload rust crates
10. [xhochy] update conda recipes
11. [
Per my other email, you can generate JSON that is canonical protobuf if you
don't want to pull the protobuf dependency. In terms of field typing: I
could see treating that as optional in a user expression that is resolved
later.
On Fri, Jul 24, 2020 at 12:47 PM Patrick Pai wrote:
> I only briefl
I only briefly looked into the Gandiva protobuf, but one issue seems to be
using protobuf (Wes is against this for dependency reasons). There's also some
inconsistencies between the Gandiva protobuf and how filter expressions should
be represented, i.e. in the Gandiva protobuf fields are typed w
Rust crates are published. This went very smoothly this time.
On Fri, Jul 24, 2020 at 11:26 AM Andy Grove wrote:
> Nver mind, I figured it out ...
> https://downloads.apache.org/arrow/arrow-1.0.0/
>
> On Fri, Jul 24, 2020 at 11:12 AM Andy Grove wrote:
>
>> Hi Krisztián,
>>
>> The checklist says
Nver mind, I figured it out ...
https://downloads.apache.org/arrow/arrow-1.0.0/
On Fri, Jul 24, 2020 at 11:12 AM Andy Grove wrote:
> Hi Krisztián,
>
> The checklist says you have already uploaded the source. Where would I
> find that? Apologies if this should be obvious or if I missed a link
> s
Hi Krisztián,
The checklist says you have already uploaded the source. Where would I find
that? Apologies if this should be obvious or if I missed a link somewhere.
Thanks,
Andy.
On Fri, Jul 24, 2020 at 8:27 AM Krisztián Szűcs
wrote:
> 1. [done] rebase master
> 2. [done] upload source
> 3.
IMO we should not make a JS release given the complications. If demand
emerges for a patched JS release, we can do it then, but since there have
been no code changes for a few releases now, I don't think it matters.
Neal
On Fri, Jul 24, 2020 at 7:51 AM Krisztián Szűcs
wrote:
> On Fri, Jul 24,
On Fri, Jul 24, 2020 at 4:36 PM Micah Kornfield wrote:
>
> Should we hold off on upgrading JS?
I'm a bit unsure. The release doesn't contain any JS patches, so theoretically:
- it should be identical with the previous one
- should work in the same node environments
While it's not essential to upd
Thanks.
On Fri, Jul 24, 2020 at 8:15 AM Neal Richardson
wrote:
> There is a 2.0.0 version in JIRA that we've been using to put things bumped
> from the 1.0.0 release, so you can use that. Though it sounds like we'll be
> doing a minor/patch release and will need a 1.1.0 or 1.0.1.
>
> Neal
>
> On
Should we hold off on upgrading JS?
On Friday, July 24, 2020, Neal Richardson
wrote:
> I'll handle R packaging and Homebrew as usual, and I'll deploy the new
> website too.
>
> Neal
>
>
> On Fri, Jul 24, 2020 at 6:08 AM Krisztián Szűcs >
> wrote:
>
> > On Fri, Jul 24, 2020 at 2:25 PM Ryan Murra
1. [done] rebase master
2. [done] upload source
3. [done] upload binaries
4. [done/PR-ready] update website
5. [done] upload ruby gems
6. [ ] upload js packages
8. [done] upload C# packages
9. [andygrove] upload rust crates
10. [xhochy] update conda recipes
11. [done] upload wheels to pypi
It's part of the release process, but I'm more than happy if you may
go ahead and create it :)
Thanks Andy!
On Fri, Jul 24, 2020 at 3:55 PM Andy Grove wrote:
>
> I assume that the next release is intended to be 1.1.0 based on the
> snapshot versions in master but this version doesn't seem to exi
I'll handle R packaging and Homebrew as usual, and I'll deploy the new
website too.
Neal
On Fri, Jul 24, 2020 at 6:08 AM Krisztián Szűcs
wrote:
> On Fri, Jul 24, 2020 at 2:25 PM Ryan Murray wrote:
> >
> > Hey Krisztian,
> >
> > I agree. I ran it on LLVM/Clang 9 and 10 and it failed both times
There is a 2.0.0 version in JIRA that we've been using to put things bumped
from the 1.0.0 release, so you can use that. Though it sounds like we'll be
doing a minor/patch release and will need a 1.1.0 or 1.0.1.
Neal
On Fri, Jul 24, 2020 at 6:38 AM Andy Grove wrote:
> I assume that the next rel
1. [done] rebase master
2. [done] upload source
3. [kszucs] upload binaries
4. [ ] update website
5. [ ] upload ruby gems
6. [ ] upload js packages
8. [ ] upload C# packages
9. [andygrove] upload rust crates
10. [uwe] update conda recipes
11. [kszucs] upload wheels to pypi
12. [ ] update ho
1. [done] rebase master
2. [done] upload source
3. [done] upload binaries
4. [done/PR-ready] update website
5. [done] upload ruby gems
6. [ ] upload js packages
8. [ ] upload C# packages
9. [andygrove] upload rust crates
10. [xhochy] update conda recipes
11. [done] upload wheels to pypi
12.
I assume that the next release is intended to be 1.1.0 based on the
snapshot versions in master but this version doesn't seem to exist in JIRA.
Should I go ahead and create it or is this something that happens as part
of the release process?
Thanks.
On Fri, Jul 24, 2020 at 2:25 PM Ryan Murray wrote:
>
> Hey Krisztian,
>
> I agree. I ran it on LLVM/Clang 9 and 10 and it failed both times. Given
> that everyone else had it succeed and there are a few tickets open around
> LLVM > 8 I suspect it is Clang. I am currently running w/ 8 to see if it
Thanks Andy! Updated the checklist:
1. [done] rebase master
2. [done] upload source
3. [kszucs] upload binaries
4. [ ] update website
5. [ ] upload ruby gems
6. [ ] upload js packages
8. [ ] upload C# packages
9. [andygrove] upload rust crates
10. [ ] update conda recipes
11. [kszucs] uplo
I can take care of the Rust release.
On Fri, Jul 24, 2020, 6:24 AM Krisztián Szűcs
wrote:
> Here is the post-release checklist, I'm working on the first three
> tasks. If anyone would like to help, please let me know.
>
> 1. [kszucs] rebase master
> 2. [kszucs] upload source
> 3. [kszucs] up
Hey Krisztian,
I agree. I ran it on LLVM/Clang 9 and 10 and it failed both times. Given
that everyone else had it succeed and there are a few tickets open around
LLVM > 8 I suspect it is Clang. I am currently running w/ 8 to see if it
passes. Do we have documents anywhere that list Gandiva's LLVM/
Here is the post-release checklist, I'm working on the first three
tasks. If anyone would like to help, please let me know.
1. [kszucs] rebase master
2. [kszucs] upload source
3. [kszucs] upload binaries
4. [ ] update website
5. [ ] upload ruby gems
6. [ ] upload js packages
8. [ ] upload C
The VOTE carries with 6 binding +1 votes and 1 non-binding +1 vote and
1 non-binding +0 vote.
I'm starting the post release tasks and keep you posted about the
remaining tasks.
Thanks everyone!
On Fri, Jul 24, 2020 at 2:16 PM Krisztián Szűcs
wrote:
>
> On Tue, Jul 21, 2020 at 3:57 PM Ryan Murra
On Tue, Jul 21, 2020 at 3:57 PM Ryan Murray wrote:
>
> +0 (non-binding)
>
>
> I verified source, release, binaries, integration tests for Python, C++,
> Java. All went fine except for a failed test in c++ Gandiva: [ FAILED ]
> TestProjector.TestDateTime
It's hard to evaluate without any context
The automatized release verification tasks have passed as well:
https://github.com/apache/arrow/pull/7814
On Fri, Jul 24, 2020 at 1:38 PM Krisztián Szűcs
wrote:
>
> +1 (binding)
>
> Verified the wheels, binaries and source on macOS 10.15
>
>
> On Thu, Jul 23, 2020 at 6:54 PM Micah Kornfield wrot
+1 (binding)
Verified the wheels, binaries and source on macOS 10.15
On Thu, Jul 23, 2020 at 6:54 PM Micah Kornfield wrote:
>
> +1 (binding)
>
> Ran on Ubuntu 19.04
>
> Verified binaries, wheels via the script.
>
> Verified sources with:
> ARROW_TMPDIR=/tmp/arrow-test TEST_DEFAULT=0 TEST_SOURC
Arrow Build Report for Job nightly-2020-07-24-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-07-24-0
Failed Tasks:
- conda-osx-clang-py38:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-07-24-0-azure-conda-osx-clang-py38
- test
27 matches
Mail list logo
