{"push_id":1466284841,"size":2,"distinct_size":2,"ref":"refs/heads/ARROW-374","head":"4a9aaf4d7a455ee79043c26a9085c92f54105896","before":"444dd3ead3ab653e106c5ade97643535ad765924","commits":[{"sha":"73455b56f705c3c11d3c29447082641dcab4c63a","author":{"name":"Uwe L. Korn","email":"c54475cbe1bd5c74633f741d1ff661d10a297631@xhochy.com"},"message":"ARROW-430: Improved version handling\n\nThis reintroduces `setuptools_scm` versioning for git clones and sdists/wheels. git-archives are handled by a separate chunk of code that will infer the version from the `pom.xml`\n\nAs in the Maven world, always the next to-be-released version is specified and Python PEP 440 development versions are based on the previous release, it used the most minimal pre-release version specified there.\n\nI would suggest to keep the conda package versioning as it is currently, i.e. manually set it to 0.1.0postX.\n\nAlso: I would rather not parse the Maven XML but that is the most simple way currently to ensure that the versioning system is in a state where we can still make releases with the Maven release plugin.\n\nAuthor: Uwe L. Korn <uwelk@xhochy.com>\n\nCloses #248 from xhochy/ARROW-430 and squashes the following commits:\n\n39753f8 [Uwe L. Korn] Infer version from java/pom.xml\n05c44ea [Uwe L. Korn] Get rid of setuptools_scm_git_archive\n14b8136 [Uwe L. Korn] Revert \"ARROW-429: Revert ARROW-379 until git-archive issues are resolved\"\n\nChange-Id: I4f6d291e63b2518af47c2a81049aa24a38c92821","distinct":true,"url":"https://api.github.com/repos/wesm/arrow/commits/73455b56f705c3c11d3c29447082641dcab4c63a"},{"sha":"4a9aaf4d7a455ee79043c26a9085c92f54105896","author":{"name":"Wes McKinney","email":"7af4275bc910f83fd113585f67f9fee33751d10a@twosigma.com"},"message":"Add Python interface to BinaryArray, convert PyBytes to binary instead of\nassuming utf8 unicode","distinct":true,"url":"https://api.github.com/repos/wesm/arrow/commits/4a9aaf4d7a455ee79043c26a9085c92f54105896"}]}
{"actor":{"display_login":"wesm"}}