[
https://issues.apache.org/jira/browse/SEDONA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jia Yu closed SEDONA-3.
---
Resolution: Fixed
> Prepare the first Sedona release
>
>
>
g
Sedona
before Christmas, we can postpone it to Sedona 1.0.1
or
1.1.0.
@everyone
Our top priority is to draw the first Sedona release
ASAP.
Users
have
been
waiting for almost six months. Let's push hard to
publish
the
first
Sedona
release to Maven Central and PyPI before Christmas.
t status:
>>> >> > >>>>>> 1. Move to JTS PR has been merged to the master branch. If
>>> JTS
>>> >> 1.18
>>> >> > >> gets
>>> >> > >>>>>> published in a few weeks, we will use the
>>> 2. Sedona doc update is in progress. I am half way there. You
>> can
>> >> > >> track
>> >> > >>>>>> the progress here:
>> >> > >> https://github.com/apache/incubator-sedona/pull/493
>> >> >
Question:
> >> > >>>>>>
> >> > >>>>>> What is the most appropriate maven artifact name for Sedona on
> >> Spark
> >> > >>>>>> 2.4? I used to put "sedona-sql_2.4". But it looks like "_2.4&quo
a-sql-spark3" for Spark 3.0?
>> > >>>>>>
>> > >>>>>> Thanks,
>> > >>>>>> Jia
>> > >>>>>>
>> > >>>>>> On Tue, Nov 24, 2020 at 8:16 AM Jim Hughes
>> >
>>
>> > >>>>>> On Tue, Nov 24, 2020 at 8:16 AM Jim Hughes
>> > wrote:
>> > >>>>>>
>> > >>>>>>> Hi all,
>> > >>>>>>>
>> > >>>>>>> Felix, good to know that a
gt; > >>>>>>> various GeoTools modules has other licenses on it. As such,
> > gt-main
> > >> is
> > >>>>>>> mostly LGPL with some BSD code as well.
> > >>>>>>>
> >
>>>> On 11/23/2020 9:50 PM, Jia Yu wrote:
> >>>>>>>> Thank you, Felix. I will use the WIP disclaimer.
> >>>>>>>>
> >>>>>>>> To answer Jim's question, GeoTools components use different
> >> licenses:
> &g
11/23/20 1:41 PM, Felix Cheung wrote:
I can help review around Dev 13 to give a first pass. It should
give
you an
easier path to IPMC vote.
On Sun, Nov 22, 2020 at 10:50 PM Jia Yu
wrote:
Hi Pawel and everyone,
Let's do this in the first Sedona release. But can you please
first
fix the
Pyt
Tools library by themselves.
> >>>>>>
> >>>>>>
> >>>>>> On Mon, Nov 23, 2020 at 6:24 PM Felix Cheung <
> felixche...@apache.org>
> >>>>> wrote:
> >>>>>>> On Mon, Nov 23, 2020 at 6:03
jnh5y commented on a change in pull request #495:
URL: https://github.com/apache/incubator-sedona/pull/495#discussion_r540217296
##
File path: core/src/main/java/org/locationtech/jts/index/quadtree/Node.java
##
@@ -0,0 +1,183 @@
+
+/*
+ * Copyright (c) 2016 Vivid Solutions.
+
ds for shipping code with licenses that it does not approve
of.
Cheers,
Jim
On 11/23/20 1:41 PM, Felix Cheung wrote:
I can help review around Dev 13 to give a first pass. It should
give
you an
easier path to IPMC vote.
On Sun, Nov 22, 2020 at 10:50 PM Jia Yu
wrote:
Hi Pawel and everyon
jiayuasu opened a new pull request #495:
URL: https://github.com/apache/incubator-sedona/pull/495
## Is this PR related to a proposed Issue?
https://issues.apache.org/jira/browse/SEDONA-3
## What changes were proposed in this PR?
1. Remove JTS Git submodule, use JTS
sclaimer
>>>> >>> https://incubator.apache.org/policy/incubation.html#releases
>>>> >>>
>>>> >>>
>>>> >>> As for the LGPL dependency specifically, a replacement will be
>>>> needed?
>>>> >>>
>&
LGPL dependency specifically, a replacement will be
>>> needed?
>>> >>>
>>> >>
>>> >> To clarify, ok to note in the WIP disclaimer- so it can be released
>>> with
>>> >> this.
>>> >>
>>>
Mon, Nov 23, 2020 at 11:15 AM Jim Hughes wrote:
>> >>>
>> >>>> Hi all,
>> >>>>
>> >>>> Has the fact that one of the dependencies is LGPL (GeoTools) been
>> >>>> discussed / addressed? (See
>> >>>> https://www.apache.or
t;>>> I'm asking since I don't know if the ASF has any recommended work
> >>>> arounds for shipping code with licenses that it does not approve of.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Jim
> >>>>
> >>
te:
I can help review around Dev 13 to give a first pass. It should give
you an
easier path to IPMC vote.
On Sun, Nov 22, 2020 at 10:50 PM Jia Yu
wrote:
Hi Pawel and everyone,
Let's do this in the first Sedona release. But can you please first
fix the
Python API for our Move-to-JTS PR, and
> >>
> > >> Cheers,
> > >>
> > >> Jim
> > >>
> > >> On 11/23/20 1:41 PM, Felix Cheung wrote:
> > >> > I can help review around Dev 13 to give a first pass. It should give
> > >> you an
> > >> > easier
elix Cheung wrote:
> >> > I can help review around Dev 13 to give a first pass. It should give
> >> you an
> >> > easier path to IPMC vote.
> >> >
> >> >
> >> > On Sun, Nov 22, 2020 at 10:50 PM Jia Yu
> wrote:
> >> >
>
s that it does not approve of.
>>
>> Cheers,
>>
>> Jim
>>
>> On 11/23/20 1:41 PM, Felix Cheung wrote:
>> > I can help review around Dev 13 to give a first pass. It should give
>> you an
>> > easier path to IPMC vote.
>> >
>>
o IPMC vote.
> >
> >
> > On Sun, Nov 22, 2020 at 10:50 PM Jia Yu wrote:
> >
> >> Hi Pawel and everyone,
> >>
> >> Let's do this in the first Sedona release. But can you please first fix
> the
> >> Python API for our Move-to-JTS PR, and the
of.
Cheers,
Jim
On 11/23/20 1:41 PM, Felix Cheung wrote:
I can help review around Dev 13 to give a first pass. It should give you an
easier path to IPMC vote.
On Sun, Nov 22, 2020 at 10:50 PM Jia Yu wrote:
Hi Pawel and everyone,
Let's do this in the first Sedona release. But can you please
Hi Pawel and everyone,
Let's do this in the first Sedona release. But can you please first fix the
Python API for our Move-to-JTS PR, and then work on this one? If this
Python RDD-DF Adapter PR might slow down our progress of releasing Sedona
before Christmas, we can postpone it to Sedona 1.0.1
branch with tests where this
functionality is available (need 3-4 days to make it 100% ready), in two
above scenarios there will be almost no difference between Python and Scala
or Java API. Should I create PR to include this feature within the first
Sedona release ?
Regards,
Paweł
pon., 16 lis 2020 o
, @Paweł Kociński
> > > , I, and probably Martin from JTS will
> take
> > > care of these PRs in the coming days.
> > > (1) Sedona PR: https://github.com/apache/incubator-sedona/pull/488
> > > (2) JTS PR: https://github.com/locationtech/jts/pull/633
> > &
he first release, I have deleted the "SNAPSHOT"
> in
> > my JTS 1.16 fork.
> > Most likely, we have to move forward with my JTS 1.16 fork in the first
> > Sedona release because of the conflict among JTStoGeoJSON, GeoTools, and
> > JTS 1.17.
> > So @Netanel Ma
release, I have deleted the "SNAPSHOT" in
my JTS 1.16 fork.
Most likely, we have to move forward with my JTS 1.16 fork in the first
Sedona release because of the conflict among JTStoGeoJSON, GeoTools, and
JTS 1.17.
So @Netanel Malka could you please do another
dry-run on the Sedona fir
ption: Description: Description:
cid:image001.jpg@01C85203.36A2AF30]
From: Felix Cheung
Sent: Wednesday, November 4, 2020 19:57
To: dev@sedona.apache.org
Cc: Jinxuan Wu; Mohamed Sarwat; Netanel Malka; Paweł Kociński; Zongsi
Zhang
Subject: Re: First Sedona release
1) No you
INFRA-21085>
>>>>> * Followed this<
>>>>> https://infra.apache.org/publishing-maven-artifacts.html> guide to test
>>>>> the maven release process
>>>>> * I hope to create a PR soon for adjusting the build to deploy to
>>>>
; Netanel Malka; Paweł Kociński; Zongsi
Zhang
Subject: 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
> > [Description: Description: Description: Description:
> > cid:image001.jpg@01C85203.36A2AF30]
> > ____________
> > From: Felix Cheung
> > Sent: Wednesday, November 4, 2020 19:57
> > To: dev@sedona.apache.org
> > Cc: Jinxuan Wu; Mohamed Sarwat;
Description:
cid:image001.jpg@01C85203.36A2AF30]
From: Felix Cheung
Sent: Wednesday, November 4, 2020 19:57
To: dev@sedona.apache.org
Cc: Jinxuan Wu; Mohamed Sarwat; Netanel Malka; Paweł Kociński; Zongsi Zhang
Subject: Re: First Sedona release
1) No you don’t ne
> 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 no
t;
> > 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 Sedon
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
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
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
39 matches
Mail list logo
