@Uwe, I think you can rebase master on top of your release branch. In the
future I'd recommend not pushing to master while we do  a release vote.
@Holden, agreed. This seems like an oversight I don't see why we should
have mockito in compile scope.
I don't think it is a release blocker though. (let us know if you think
otherwise)
I opened a bug: https://issues.apache.org/jira/browse/ARROW-562


On Tue, Feb 14, 2017 at 2:25 PM, Holden Karau <[email protected]> wrote:

> -0 (non-binding): mockito in compile scope may make this difficult for
> downstream users to package in their projects.
>
> On Tue, Feb 14, 2017 at 2:10 PM, Uwe L. Korn <[email protected]> wrote:
>
> > I think the problem is that there are two commits in the release branch
> > (which I have not pushed to the asf git yet) that were auto generated by
> > maven that update the version numbers. I thought that those should be
> > pushed once the vote passes. But we sadly did already push other commits
> on
> > master so we're in a diverging state here.
> >
> > > Am 14.02.2017 um 22:24 schrieb Wes McKinney <[email protected]>:
> > >
> > > Julien -- it looks like we may need to update some of the Java POM
> > > metadata. Can you confirm?
> > >
> > >> On Tue, Feb 14, 2017 at 2:40 PM, Julien Le Dem <[email protected]>
> > wrote:
> > >> +1 (binding)
> > >>
> > >>> On Tue, Feb 14, 2017 at 10:10 AM, Bryan Cutler <[email protected]>
> > wrote:
> > >>>
> > >>> I have
> > >>> * Built C++ and run unit tests
> > >>> * Built Python and run unit tests
> > >>> * Built Java and run unit tests
> > >>> * Run integration tests
> > >>> * Tested with Spark integration from SPARK-13534
> > >>>
> > >>> My vote: +1 (non-binding)
> > >>>
> > >>> Thanks!
> > >>>
> > >>>> On Tue, Feb 14, 2017 at 5:31 AM, Wes McKinney <[email protected]>
> > wrote:
> > >>>>
> > >>>> hi Uwe,
> > >>>>
> > >>>> I committed the patch to git and committed the new KEYS file to
> > >>>> https://dist.apache.org/repos/dist/release/arrow
> > >>>>
> > >>>> - Wes
> > >>>>
> > >>>>> On Tue, Feb 14, 2017 at 2:30 AM, Uwe L. Korn <[email protected]>
> > wrote:
> > >>>>> Uploaded my fingerprint to https://people.apache.org/
> > >>> keys/committer/uwe,
> > >>>>> awaiting the daily sync. Also I made a PR to add my key to the KEYS
> > >>>>> file: https://issues.apache.org/jira/browse/ARROW-558 I'll need a
> > PMC
> > >>> to
> > >>>>> merge and update SVN.
> > >>>>>
> > >>>>> --
> > >>>>>  Uwe L. Korn
> > >>>>>  [email protected]
> > >>>>>
> > >>>>>> On Mon, Feb 13, 2017, at 11:08 PM, Julien Le Dem wrote:
> > >>>>>> Did you publish your public key?
> > >>>>>> also consider adding it here: http://www.apache.org/dist/
> arrow/KEYS
> > >>>>>> and here: https://people.apache.org/keys/committer/uwe
> > >>>>>>
> > >>>>>> $ gpg --verify apache-arrow-0.2.0.tar.gz.asc
> > >>>>>> gpg: assuming signed data in `apache-arrow-0.2.0.tar.gz'
> > >>>>>> gpg: Signature made Mon Feb 13 08:40:38 2017 PST using RSA key ID
> > >>>>>> 8CAAD602
> > >>>>>> gpg: Can't check signature: public key not found
> > >>>>>>
> > >>>>>> On Mon, Feb 13, 2017 at 9:25 AM, Uwe L. Korn <[email protected]>
> > >>> wrote:
> > >>>>>>
> > >>>>>>> Hello all,
> > >>>>>>>
> > >>>>>>> I'd like to propose the first release candidate (rc1) of Apache
> > >>> Arrow
> > >>>>>>> version 0.2.0.
> > >>>>>>> It covers a total of 188 resolved JIRAs [1] Thanks to everyone
> who
> > >>>>>>> contributed to this release.
> > >>>>>>>
> > >>>>>>> The source release rc1 is hosted at [2].
> > >>>>>>> This release candidate is based on commit
> > >>>>>>> 66f650cd359e13f3d5c3d4ef78d89f389d6bcecc located at [3].
> > >>>>>>>
> > >>>>>>> The vote will be open for the next ~72 hours ending at 19:00 CET,
> > >>>>>>> February 16, 2017.
> > >>>>>>>
> > >>>>>>> [ ] +1
> > >>>>>>> [ ] +0
> > >>>>>>> [ ] -1
> > >>>>>>>
> > >>>>>>> I have run the java build + tests
> > >>>>>>> I have run cpp build + tests
> > >>>>>>> I have built the Python manylinux1 package + run the tests
> > >>>>>>>
> > >>>>>>> Here's my vote: +1 (non-binding)
> > >>>>>>>
> > >>>>>>> Thanks,
> > >>>>>>> Uwe
> > >>>>>>>
> > >>>>>>> How to validate a release signature:
> > >>>>>>> https://httpd.apache.org/dev/verification.html
> > >>>>>>>
> > >>>>>>> [1]
> > >>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%
> > >>>>>>> 3D%20ARROW%20AND%20fixVersion%20%3D%200.2.0%20ORDER%20BY%
> > >>>> 20priority%20DESC
> > >>>>>>> [2] https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.
> > >>>> 2.0-rc1/
> > >>>>>>> [3]
> > >>>>>>> https://github.com/apache/arrow/commit/
> > >>> 66f650cd359e13f3d5c3d4ef78d89f
> > >>>>>>> 389d6bcecc
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> Julien
> > >>>>
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Julien
> >
> >
>
>
> --
> Cell : 425-233-8271
> Twitter: https://twitter.com/holdenkarau
>



-- 
Julien

Reply via email to