The motion carries with 5 binding +1 and 2 non-binding +1 and no other votes
We need to make sure this is properly documented in time for the 1.0.0 release
https://issues.apache.org/jira/browse/ARROW-6164
On Sun, Aug 4, 2019 at 5:04 PM Jacques Nadeau wrote:
>
> Looks good. +1 from me. Thanks
Looks good. +1 from me. Thanks for driving this to conclusion.
On Wed, Jul 31, 2019, 12:04 PM Bryan Cutler wrote:
> +1 (non-binding)
>
> On Wed, Jul 31, 2019 at 8:59 AM Uwe L. Korn wrote:
>
> > +1 from me.
> >
> > I really like the separate versions
> >
> > Uwe
> >
> > On Tue, Jul 30, 2019, at
+1 (non-binding)
On Wed, Jul 31, 2019 at 8:59 AM Uwe L. Korn wrote:
> +1 from me.
>
> I really like the separate versions
>
> Uwe
>
> On Tue, Jul 30, 2019, at 2:21 PM, Antoine Pitrou wrote:
> >
> > +1 from me.
> >
> > Regards
> >
> > Antoine.
> >
> >
> >
> > On Fri, 26 Jul 2019 14:33:30 -0500
>
+1 from me.
I really like the separate versions
Uwe
On Tue, Jul 30, 2019, at 2:21 PM, Antoine Pitrou wrote:
>
> +1 from me.
>
> Regards
>
> Antoine.
>
>
>
> On Fri, 26 Jul 2019 14:33:30 -0500
> Wes McKinney wrote:
> > hello,
> >
> > As discussed on the mailing list thread [1], Micah
+1 from me.
Regards
Antoine.
On Fri, 26 Jul 2019 14:33:30 -0500
Wes McKinney wrote:
> hello,
>
> As discussed on the mailing list thread [1], Micah Kornfield has
> proposed a version scheme for the project to take effect starting with
> the 1.0.0 release. See document [2] containing a
On Mon, Jul 29, 2019 at 4:28 PM Sutou Kouhei wrote:
>
> +1
>
> But I want to confirm the following:
>
> > 2. SEMANTIC VERSIONING: We follow https://semver.org/ with regards to
> > communicating library API changes. Given the project's pace of
> > evolution, most releases are likely to be MAJOR
+1
But I want to confirm the following:
> 2. SEMANTIC VERSIONING: We follow https://semver.org/ with regards to
> communicating library API changes. Given the project's pace of
> evolution, most releases are likely to be MAJOR releases according to
> SemVer principles.
We'll release 2.0.0 as
On Mon, Jul 29, 2019 at 8:07 AM Antoine Pitrou wrote:
>
>
> Le 26/07/2019 à 21:33, Wes McKinney a écrit :
> > To summarize my understanding of the plan:
> >
> > 1. TWO VERSIONS: As of 1.0.0, we establish separate FORMAT and LIBRARY
> > versions. Currently there is only a single version number.
>
Do we bump the library version on changes from _any_ language
implementation, or just the C++/Java version?
François
On Fri, Jul 26, 2019 at 3:34 PM Wes McKinney wrote:
>
> hello,
>
> As discussed on the mailing list thread [1], Micah Kornfield has
> proposed a version scheme for the project to
Le 26/07/2019 à 21:33, Wes McKinney a écrit :
> To summarize my understanding of the plan:
>
> 1. TWO VERSIONS: As of 1.0.0, we establish separate FORMAT and LIBRARY
> versions. Currently there is only a single version number.
>
> 2. SEMANTIC VERSIONING: We follow https://semver.org/ with
+1 (non-binding) Adopt these version conventions and compatibility
guarantees as of Apache Arrow 1.0.0
On Fri, Jul 26, 2019 at 12:34 PM Wes McKinney wrote:
> hello,
>
> As discussed on the mailing list thread [1], Micah Kornfield has
> proposed a version scheme for the project to take effect
hello,
As discussed on the mailing list thread [1], Micah Kornfield has
proposed a version scheme for the project to take effect starting with
the 1.0.0 release. See document [2] containing a discussion of the
issues involved.
To summarize my understanding of the plan:
1. TWO VERSIONS: As of
12 matches
Mail list logo
