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 <jam...@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 | jam...@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.
