You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by James Duong <ja...@bitquilltech.com> on 2020/11/03 00:11:44 UTC
Arrow 2.0.0 versioning
Hi,
I noticed that in the Java POM files, the version in master is still 2.0.0
even after the release. This patch updated versions to 3.0.0-SNAPSHOT in
other languages:
https://github.com/apache/arrow/commit/b1f36acca85d0845c1e64c0a3270651d4a1467b7
--
*James Duong*
Lead Software Developer
Bit Quill Technologies Inc.
Direct: +1.604.562.6082 | jamesd@bitquilltech.com
https://www.bitquilltech.com
This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure, or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message. Thank you.
Re: Arrow 2.0.0 versioning
Posted by James Duong <ja...@bitquilltech.com>.
Thanks. I ran the command and created a PR:
https://github.com/apache/arrow/pull/8577
On Mon, Nov 2, 2020 at 11:14 PM Krisztián Szűcs <sz...@gmail.com>
wrote:
> On Tue, Nov 3, 2020 at 5:07 AM James Duong <ja...@bitquilltech.com>
> wrote:
> >
> > I can go ahead and make the change, but should this get force pushed
> > earlier in the history to be right after the Arrow 2 commit that was
> tagged?
> Something most have gone wrong during the maven release preparation.
> `mvn versions:set -DnewVersion=3.0.0-SNAPSHOT` should set up the
> versions properly.
>
> If we want to be pedantic then a rebase would be nice, but it may be
> distracting for contributors since they would need to rebase their PRs
> as well. I'd say that we can omit it.
> >
> > The reason I ran into this was that I had a local build of master which
> had
> > interface changes that weren't in the Arrow 2 maven artifacts.
> >
> > On Mon, Nov 2, 2020, 19:08 Wes McKinney <we...@gmail.com> wrote:
> >
> > > The parts of the release process involving Maven are brittle and error
> > > prone, so it probably just didn't flow through properly, or the commit
> > > updating the Java POM versions didn't get pushed to the release branch
> > > or something similar
> > >
> > > On Mon, Nov 2, 2020 at 6:12 PM James Duong <ja...@bitquilltech.com>
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I noticed that in the Java POM files, the version in master is still
> > > 2.0.0
> > > > even after the release. This patch updated versions to
> 3.0.0-SNAPSHOT in
> > > > other languages:
> > > >
> > >
> https://github.com/apache/arrow/commit/b1f36acca85d0845c1e64c0a3270651d4a1467b7
> > > >
> > > >
> > > > --
> > > >
> > > > *James Duong*
> > > > Lead Software Developer
> > > > Bit Quill Technologies Inc.
> > > > Direct: +1.604.562.6082 | jamesd@bitquilltech.com
> > > > https://www.bitquilltech.com
> > > >
> > > > This email message is for the sole use of the intended recipient(s)
> and
> > > may
> > > > contain confidential and privileged information. Any unauthorized
> > > review,
> > > > use, disclosure, or distribution is prohibited. If you are not the
> > > > intended recipient, please contact the sender by reply email and
> destroy
> > > > all copies of the original message. Thank you.
> > >
>
--
*James Duong*
Lead Software Developer
Bit Quill Technologies Inc.
Direct: +1.604.562.6082 | jamesd@bitquilltech.com
https://www.bitquilltech.com
This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure, or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message. Thank you.
Re: Arrow 2.0.0 versioning
Posted by Krisztián Szűcs <sz...@gmail.com>.
On Tue, Nov 3, 2020 at 5:07 AM James Duong <ja...@bitquilltech.com> wrote:
>
> I can go ahead and make the change, but should this get force pushed
> earlier in the history to be right after the Arrow 2 commit that was tagged?
Something most have gone wrong during the maven release preparation.
`mvn versions:set -DnewVersion=3.0.0-SNAPSHOT` should set up the
versions properly.
If we want to be pedantic then a rebase would be nice, but it may be
distracting for contributors since they would need to rebase their PRs
as well. I'd say that we can omit it.
>
> The reason I ran into this was that I had a local build of master which had
> interface changes that weren't in the Arrow 2 maven artifacts.
>
> On Mon, Nov 2, 2020, 19:08 Wes McKinney <we...@gmail.com> wrote:
>
> > The parts of the release process involving Maven are brittle and error
> > prone, so it probably just didn't flow through properly, or the commit
> > updating the Java POM versions didn't get pushed to the release branch
> > or something similar
> >
> > On Mon, Nov 2, 2020 at 6:12 PM James Duong <ja...@bitquilltech.com>
> > wrote:
> > >
> > > Hi,
> > >
> > > I noticed that in the Java POM files, the version in master is still
> > 2.0.0
> > > even after the release. This patch updated versions to 3.0.0-SNAPSHOT in
> > > other languages:
> > >
> > https://github.com/apache/arrow/commit/b1f36acca85d0845c1e64c0a3270651d4a1467b7
> > >
> > >
> > > --
> > >
> > > *James Duong*
> > > Lead Software Developer
> > > Bit Quill Technologies Inc.
> > > Direct: +1.604.562.6082 | jamesd@bitquilltech.com
> > > https://www.bitquilltech.com
> > >
> > > This email message is for the sole use of the intended recipient(s) and
> > may
> > > contain confidential and privileged information. Any unauthorized
> > review,
> > > use, disclosure, or distribution is prohibited. If you are not the
> > > intended recipient, please contact the sender by reply email and destroy
> > > all copies of the original message. Thank you.
> >
Re: Arrow 2.0.0 versioning
Posted by James Duong <ja...@bitquilltech.com>.
I can go ahead and make the change, but should this get force pushed
earlier in the history to be right after the Arrow 2 commit that was tagged?
The reason I ran into this was that I had a local build of master which had
interface changes that weren't in the Arrow 2 maven artifacts.
On Mon, Nov 2, 2020, 19:08 Wes McKinney <we...@gmail.com> wrote:
> The parts of the release process involving Maven are brittle and error
> prone, so it probably just didn't flow through properly, or the commit
> updating the Java POM versions didn't get pushed to the release branch
> or something similar
>
> On Mon, Nov 2, 2020 at 6:12 PM James Duong <ja...@bitquilltech.com>
> wrote:
> >
> > Hi,
> >
> > I noticed that in the Java POM files, the version in master is still
> 2.0.0
> > even after the release. This patch updated versions to 3.0.0-SNAPSHOT in
> > other languages:
> >
> https://github.com/apache/arrow/commit/b1f36acca85d0845c1e64c0a3270651d4a1467b7
> >
> >
> > --
> >
> > *James Duong*
> > Lead Software Developer
> > Bit Quill Technologies Inc.
> > Direct: +1.604.562.6082 | jamesd@bitquilltech.com
> > https://www.bitquilltech.com
> >
> > This email message is for the sole use of the intended recipient(s) and
> may
> > contain confidential and privileged information. Any unauthorized
> review,
> > use, disclosure, or distribution is prohibited. If you are not the
> > intended recipient, please contact the sender by reply email and destroy
> > all copies of the original message. Thank you.
>
Re: Arrow 2.0.0 versioning
Posted by Wes McKinney <we...@gmail.com>.
The parts of the release process involving Maven are brittle and error
prone, so it probably just didn't flow through properly, or the commit
updating the Java POM versions didn't get pushed to the release branch
or something similar
On Mon, Nov 2, 2020 at 6:12 PM James Duong <ja...@bitquilltech.com> wrote:
>
> Hi,
>
> I noticed that in the Java POM files, the version in master is still 2.0.0
> even after the release. This patch updated versions to 3.0.0-SNAPSHOT in
> other languages:
> https://github.com/apache/arrow/commit/b1f36acca85d0845c1e64c0a3270651d4a1467b7
>
>
> --
>
> *James Duong*
> Lead Software Developer
> Bit Quill Technologies Inc.
> Direct: +1.604.562.6082 | jamesd@bitquilltech.com
> https://www.bitquilltech.com
>
> This email message is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. Any unauthorized review,
> use, disclosure, or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply email and destroy
> all copies of the original message. Thank you.