Podling Sedona Report Reminder - November 2020

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 18 November 2020. The report for your podling will form a part of th

Re: Podling Sedona Report Reminder - November 2020

I have submitted the November podling report. We mainly focused on the first release of Sedona. I believe we can deliver our first release before December. Mentors, again, thank you for your help! On Sun, Nov 1, 2020 at 11:39 AM Felix Cheung wrote: > Reminder. > > __

Re: First Sedona release

1) No you don’t need KEYS file in github only on the release share https://dist.apache.org/repos/dist/dev/incubator/ 2) as podling you add to https://dist.apache.org/repos/dist/dev/incubator/ When you commit via svn you will be able to add a “directory” for Sedona 2a) for release, you basically d

[GitHub] [incubator-sedona] Imbruced commented on pull request #487: [Sedona-3] Sedona release 3.0 python adapter [WIP]

Imbruced commented on pull request #487: URL: https://github.com/apache/incubator-sedona/pull/487#issuecomment-721870578 @jiayuasu It's ready to review. This is an automated message from the Apache Git Service. To respond to

Re: First Sedona release

Hi, I followed the release-signing doc and created a key for signing and hashing. I have a few questions: 1. Should the KEYS file also be added to the project root directory on Github? ( I saw it in Apache Ant) 2. I saw in release-policy_u