Hi Netanel, Pawel and other committers, While Pawel is working on Python code of Sedona 1.0, let's focus on other parts required by the release. Netanel, can you help me with all the ASF incubator requirement items that are not DONE?
*Here is a checklist for our first Sedona release* *ASF incubator requirement (https://incubator.apache.org/guides/releasemanagement.html <https://incubator.apache.org/guides/releasemanagement.html>, we probably should read ASF release requirement as well):* 1 .Include the word incubating in the release file name: DONE. Please see the POM.xml in all directories. 2. Include an ASF LICENSE and NOTICE file: DONE. Please see the GitHub repo. 3. Have valid checksums or signatures: I believe signature should be done by the GPG key. Not sure about the checksum. I am also not sure about the GPG key requirement of ASF. I use GPG key to sign releases of GeoSpark in the past. 4. Be placed in the correct place on the ASF’s infrastructure: we should place our releases in two places: Maven, and PyPi. Not sure how to relate them to ASF. 5. Have a KEYS file to validate the release: this should be the public key of our GPG key? *Sedona requirement* 1. Python path name, file headers, and jars 2. Project website docs: documentation should use the name, Sedona, in all tutorials. We should also include the situation of GeoTools dependencies. Thanks, Jia On Wed, Oct 14, 2020 at 10:08 PM Jia Yu <[email protected]> wrote: > Hi folks, > > We will be working on the first Sedona. Please see the JIRA ticket here: > https://issues.apache.org/jira/projects/SEDONA/issues/SEDONA-3?filter=allopenissues > > Do you think there are any outstanding issues to be fixed as well? > > Thanks, > Jia >
