[
https://issues.apache.org/jira/browse/SEDONA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634083#comment-17634083
]
Jia Yu commented on SEDONA-194:
---
This sounds like a good idea. I will do it!
> Merge
Hi Martin,
I don't think this is a blocker and we can put it in the next release. It
is kind of complicated to create another release candidate unless there is
a critical bug or it misses required components for an Apache release.
Hope this makes sense :-)
Jia
On Mon, Nov 14, 2022 at 3:13 AM
Martin Andersson created SEDONA-194:
---
Summary: Merge org.datasyslab.sernetcdf into Sedona
Key: SEDONA-194
URL: https://issues.apache.org/jira/browse/SEDONA-194
Project: Apache Sedona
Issue
Hi all,
Should SEDONA-193 be considered a blocker for the release?
It's a correctness issue and a regression from sedona-1.2.1.
/Martin
Den mån 14 nov. 2022 kl 03:18 skrev Kengo Seki :
> +1 (binding)
>
> I checked:
> * Download links are valid
> * Checksums and PGP signatures are valid
> *
[
https://issues.apache.org/jira/browse/SEDONA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17633648#comment-17633648
]
Martin Andersson commented on SEDONA-193:
-
This is a regression similar to SEDONA-182. I haven't
umartin opened a new pull request, #713:
URL: https://github.com/apache/incubator-sedona/pull/713
## Did you read the Contributor Guide?
- Yes, I have read [Contributor
Rules](https://sedona.apache.org/community/rule/) and [Contributor Development
Martin Andersson created SEDONA-193:
---
Summary: Regression in ST_AsBinary
Key: SEDONA-193
URL: https://issues.apache.org/jira/browse/SEDONA-193
Project: Apache Sedona
Issue Type: Bug
