Hi, > For Python release "apache_gravitino-0.6.0.tar.gz" version, as far as I > know, Python doesn't support version like "0.6.0-incubating", so I only > keep the 0.6.0 delibrately. I also refer to some other incubating projects > like HugeGraph (https://pypi.org/project/hugegraph-python/#history), seems > they also don't add the "incubating" in their version.
We must change this (easy enough to do with "svn mv") as all artifacts need ”incubating” in their name. See [1] "The release archive(s) MUST include the word "incubating" in the filename." I’ll ask HugeGraph to also fix this. Sure I can help out on the LICENSE and NOTICE issues. I’ve raised an issue for it. > The local compile works for me. I'm not so sure about which file has the > issues. I’ll raise an issue with the details. > It will be there when we have an official release. It needs to be there while voting on the release. Several other incubating projects have been asked to fix this in recent times. >> - The Python client README.md build instruction needs to be updated as >> they assume it part of the main gravitino repo >> >> > Python README.md already reflects the Python things including how to build > Python package, can you please point out what specific issue it is? Its context is outside of that one artifact, which would be confusing to someone who comes across the package on its own. For instance, if I go to "Build and testing”, which someone might do when reviewing the artifact, and it says "./gradlew :clients:client-python:build”, however that is not going to work in this artifact. Kind Regards, Justin 1. https://incubator.apache.org/policy/incubation.html#releases
