You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by "Uwe L. Korn" <uw...@xhochy.com> on 2018/04/17 15:40:10 UTC
Requirements for a 0.9.1 release
Hello all,
I would like to do a 0.9.1 release as soon as possible. For this the minimum required steps are that we have the following issues resolved:
* https://issues.apache.org/jira/browse/ARROW-1975 (expect the PR for this today or tomorrow morning)
* https://issues.apache.org/jira/browse/ARROW-2352
I would do the release from the current master as the ABI checks should ensure that we don't have any breakages on the C++ side and I have seen no breaking API changes in Python. While we may not have the full build system that Krisztián is working on, I will try to use it to build the binaries (or use the arrow-dist repository) so that we can also vote on the binaries. While we may not yet release them as official binaries afterwards, it should ensure that we won't come into the state we had with the last release.
As this is a patch release, I would exclude the newly added Go and Rust implementations from it.
Uwe
Re: Requirements for a 0.9.1 release
Posted by Wes McKinney <we...@gmail.com>.
hi Uwe,
> As this is a patch release, I would exclude the newly added Go and Rust implementations from it.
Do you intend to modify the source release scripts? The Go
implementations include some code from the Go project (this needs to
be included in the LICENSE file), but otherwise it might be worth
making sure the IP documentation is up to date.
I haven't been following the patches very closely this month, but I'm
concerned about this new API that was added:
https://github.com/apache/arrow/blob/master/cpp/src/arrow/ipc/message.h#L184
In the ABI review, this API should be marked as subject to change. I
can look more closely in a couple weeks, but we may be able to remove
the "aligned" argument. At minimum, the order of the arguments needs
to be changed (and perhaps introduce an IpcOptions struct).
Thanks
Wes
On Wed, Apr 18, 2018 at 12:57 AM, Bryan Cutler <cu...@gmail.com> wrote:
> Sounds good Uwe. There were a couple of recent bug fixes that were
> blockers for me, but those are done now and looking good. I do want to run
> Spark integration tests before a RC is cut, so I'll try to do that
> tomorrow. Thanks!
>
> Bryan
>
> On Tue, Apr 17, 2018 at 3:20 PM, Antoine Pitrou <an...@python.org> wrote:
>
>>
>> This sounds good to me.
>>
>> Regards
>>
>> Antoine.
>>
>>
>> Le 17/04/2018 à 17:40, Uwe L. Korn a écrit :
>> > Hello all,
>> >
>> > I would like to do a 0.9.1 release as soon as possible. For this the
>> minimum required steps are that we have the following issues resolved:
>> >
>> > * https://issues.apache.org/jira/browse/ARROW-1975 (expect the PR for
>> this today or tomorrow morning)
>> > * https://issues.apache.org/jira/browse/ARROW-2352
>> >
>> > I would do the release from the current master as the ABI checks should
>> ensure that we don't have any breakages on the C++ side and I have seen no
>> breaking API changes in Python. While we may not have the full build system
>> that Krisztián is working on, I will try to use it to build the binaries
>> (or use the arrow-dist repository) so that we can also vote on the
>> binaries. While we may not yet release them as official binaries
>> afterwards, it should ensure that we won't come into the state we had with
>> the last release.
>> >
>> > As this is a patch release, I would exclude the newly added Go and Rust
>> implementations from it.
>> >
>> > Uwe
>> >
>>
Re: Requirements for a 0.9.1 release
Posted by Bryan Cutler <cu...@gmail.com>.
Sounds good Uwe. There were a couple of recent bug fixes that were
blockers for me, but those are done now and looking good. I do want to run
Spark integration tests before a RC is cut, so I'll try to do that
tomorrow. Thanks!
Bryan
On Tue, Apr 17, 2018 at 3:20 PM, Antoine Pitrou <an...@python.org> wrote:
>
> This sounds good to me.
>
> Regards
>
> Antoine.
>
>
> Le 17/04/2018 à 17:40, Uwe L. Korn a écrit :
> > Hello all,
> >
> > I would like to do a 0.9.1 release as soon as possible. For this the
> minimum required steps are that we have the following issues resolved:
> >
> > * https://issues.apache.org/jira/browse/ARROW-1975 (expect the PR for
> this today or tomorrow morning)
> > * https://issues.apache.org/jira/browse/ARROW-2352
> >
> > I would do the release from the current master as the ABI checks should
> ensure that we don't have any breakages on the C++ side and I have seen no
> breaking API changes in Python. While we may not have the full build system
> that Krisztián is working on, I will try to use it to build the binaries
> (or use the arrow-dist repository) so that we can also vote on the
> binaries. While we may not yet release them as official binaries
> afterwards, it should ensure that we won't come into the state we had with
> the last release.
> >
> > As this is a patch release, I would exclude the newly added Go and Rust
> implementations from it.
> >
> > Uwe
> >
>
Re: Requirements for a 0.9.1 release
Posted by Antoine Pitrou <an...@python.org>.
This sounds good to me.
Regards
Antoine.
Le 17/04/2018 à 17:40, Uwe L. Korn a écrit :
> Hello all,
>
> I would like to do a 0.9.1 release as soon as possible. For this the minimum required steps are that we have the following issues resolved:
>
> * https://issues.apache.org/jira/browse/ARROW-1975 (expect the PR for this today or tomorrow morning)
> * https://issues.apache.org/jira/browse/ARROW-2352
>
> I would do the release from the current master as the ABI checks should ensure that we don't have any breakages on the C++ side and I have seen no breaking API changes in Python. While we may not have the full build system that Krisztián is working on, I will try to use it to build the binaries (or use the arrow-dist repository) so that we can also vote on the binaries. While we may not yet release them as official binaries afterwards, it should ensure that we won't come into the state we had with the last release.
>
> As this is a patch release, I would exclude the newly added Go and Rust implementations from it.
>
> Uwe
>
Re: Requirements for a 0.9.1 release
Posted by Jacques Nadeau <ja...@apache.org>.
Sounds good. +1
On Tue, Apr 17, 2018 at 8:40 AM, Uwe L. Korn <uw...@xhochy.com> wrote:
> Hello all,
>
> I would like to do a 0.9.1 release as soon as possible. For this the
> minimum required steps are that we have the following issues resolved:
>
> * https://issues.apache.org/jira/browse/ARROW-1975 (expect the PR for
> this today or tomorrow morning)
> * https://issues.apache.org/jira/browse/ARROW-2352
>
> I would do the release from the current master as the ABI checks should
> ensure that we don't have any breakages on the C++ side and I have seen no
> breaking API changes in Python. While we may not have the full build system
> that Krisztián is working on, I will try to use it to build the binaries
> (or use the arrow-dist repository) so that we can also vote on the
> binaries. While we may not yet release them as official binaries
> afterwards, it should ensure that we won't come into the state we had with
> the last release.
>
> As this is a patch release, I would exclude the newly added Go and Rust
> implementations from it.
>
> Uwe
>