Fwd: CRAN package SparkR

[Felix Cheung]

It looks like they would not allow caching the Spark
Distribution.

I’m not sure what can be done about this.

If I recall, the package should remove this during test. Or maybe
spark.install() ie optional (hence getting user confirmation?)


-- Forwarded message -
Date: Sun, Jun 13, 2021 at 10:19 PM
Subject: CRAN package SparkR
To: Felix Cheung 
CC: 


Dear maintainer,

Checking this apparently creates the default directory as per

#' @param localDir a local directory where Spark is installed. The
directory con
tains
#' version-specific folders of Spark packages. Default is
path t
o
#' the cache directory:
#' \itemize{
#'   \item Mac OS X: \file{~/Library/Caches/spark}
#'   \item Unix: \env{$XDG_CACHE_HOME} if defined,
otherwise \file{~/.cache/spark}
#'   \item Windows:
\file{\%LOCALAPPDATA\%\\Apache\\Spark\\Cache}.
#' }

However, the CRAN Policy says

  - Packages should not write in the user’s home filespace (including
clipboards), nor anywhere else on the file system apart from the R
session’s temporary directory (or during installation in the
location pointed to by TMPDIR: and such usage should be cleaned
up). Installing into the system’s R installation (e.g., scripts to
its bin directory) is not allowed.

Limited exceptions may be allowed in interactive sessions if the
package obtains confirmation from the user.

For R version 4.0 or later (hence a version dependency is required
or only conditional use is possible), packages may store
user-specific data, configuration and cache files in their
respective user directories obtained from tools::R_user_dir(),
provided that by default sizes are kept as small as possible and the
contents are actively managed (including removing outdated
material).

Can you pls fix as necessary?

Please fix before 2021-06-28 to safely retain your package on CRAN.

Best
-k

Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

[Felix Cheung]

+1

On Fri, Jun 11, 2021 at 4:18 AM Xun Liu  wrote:

> +1
> Pinot is an open source project with a broad user base, and the community
> is also very active.
>
> Best regards
> Xun Liu
>
> On Fri, Jun 11, 2021 at 7:16 PM Xun Liu  wrote:
>
> > Pinot is an open source project with a broad user base, and the community
> > is also very active.
> >
> > On Fri, Jun 11, 2021 at 6:29 PM Jim Jagielski  wrote:
> >
> >> +1 (binding)
> >>
> >> > On Jun 10, 2021, at 7:12 PM, Mayank Shrivastava 
> >> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > After a discussion with the community [1], voting [2], and a positive
> >> vote result [3],
> >> > we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
> >> > and we'd like to bring it up in discussion with the IPMC.
> >> >
> >> > To list a few of the community's achievements:
> >> >
> >> > 7800+ contributions from 168 contributors
> >> > 7 releases by various release managers
> >> > 6 new committers and 2 new PPMCs invited (all accepted)
> >> > Diverse committers and PPMCs (from 7 companies/institutes)
> >> > Apache website setup [4]
> >> > Dev conversations at dev@pinot.apache.org  dev@pinot.apache.org>
> >> > Assessed ourselves against the Apache Project maturity matrix [5]
> >> > We have built a meritocratic and open collaborative process (the
> Apache
> >> way)
> >> >
> >> > [1] Community Discussion for Graduation <
> >>
> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [2] Voting Thread <
> >>
> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [3] Voting Result <
> >>
> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [4] https://pinot.incubator.apache.org/ <
> >> https://pinot.incubator.apache.org/>
> >> > [5] Maturity Model Assessment <
> >>
> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
> >> >
> >> > Please see the proposed board resolution below and let us know what
> you
> >> > think.
> >> >
> >> > The discussion will remain open for at least 72 hours.
> >> >
> >> > ---
> >> >
> >> > Establish the Apache Pinot Project
> >> >
> >> > WHEREAS, the Board of Directors deems it to be in the best interests
> of
> >> the Foundation and consistent with the Foundation's purpose to
> establish a
> >> Project Management Committee charged with the creation and maintenance
> of
> >> open-source software, for distribution at no charge to the public,
> related
> >> to a distributed data integration framework that simplifies common
> aspects
> >> of big data integration such as data ingestion, replication,
> organization
> >> and lifecycle management for both streaming and batch data ecosystems.
> >> >
> >> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Pinot Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >> >
> >> > RESOLVED, that the Apache Pinot Project be and hereby is responsible
> >> for the creation and maintenance of software related to distributed OLAP
> >> data store to provide Real-time Analytics to power wide variety of
> >> analytical use case; and be it further
> >> >
> >> > RESOLVED, that the office of "Vice President, Apache Pinot" be and
> >> hereby is created, the person holding such office to serve at the
> direction
> >> of the Board of Directors as the chair of the Apache Pinot Project, and
> to
> >> have primary responsibility for management of the projects within the
> scope
> >> of responsibility of the Apache Pinot Project; and be it further
> >> >
> >> > RESOLVED, that the persons listed immediately below be and hereby are
> >> appointed to serve as the initial members of the Apache Pinot Project:
> >> > Felix Cheung mailto:felixche...@apache.org>>
> >> > Jackie J

Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

[Felix Cheung]

+1

On Fri, Jun 11, 2021 at 4:18 AM Xun Liu  wrote:

> +1
> Pinot is an open source project with a broad user base, and the community
> is also very active.
>
> Best regards
> Xun Liu
>
> On Fri, Jun 11, 2021 at 7:16 PM Xun Liu  wrote:
>
> > Pinot is an open source project with a broad user base, and the community
> > is also very active.
> >
> > On Fri, Jun 11, 2021 at 6:29 PM Jim Jagielski  wrote:
> >
> >> +1 (binding)
> >>
> >> > On Jun 10, 2021, at 7:12 PM, Mayank Shrivastava 
> >> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > After a discussion with the community [1], voting [2], and a positive
> >> vote result [3],
> >> > we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
> >> > and we'd like to bring it up in discussion with the IPMC.
> >> >
> >> > To list a few of the community's achievements:
> >> >
> >> > 7800+ contributions from 168 contributors
> >> > 7 releases by various release managers
> >> > 6 new committers and 2 new PPMCs invited (all accepted)
> >> > Diverse committers and PPMCs (from 7 companies/institutes)
> >> > Apache website setup [4]
> >> > Dev conversations at d...@pinot.apache.org  d...@pinot.apache.org>
> >> > Assessed ourselves against the Apache Project maturity matrix [5]
> >> > We have built a meritocratic and open collaborative process (the
> Apache
> >> way)
> >> >
> >> > [1] Community Discussion for Graduation <
> >>
> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [2] Voting Thread <
> >>
> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [3] Voting Result <
> >>
> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [4] https://pinot.incubator.apache.org/ <
> >> https://pinot.incubator.apache.org/>
> >> > [5] Maturity Model Assessment <
> >>
> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
> >> >
> >> > Please see the proposed board resolution below and let us know what
> you
> >> > think.
> >> >
> >> > The discussion will remain open for at least 72 hours.
> >> >
> >> > ---
> >> >
> >> > Establish the Apache Pinot Project
> >> >
> >> > WHEREAS, the Board of Directors deems it to be in the best interests
> of
> >> the Foundation and consistent with the Foundation's purpose to
> establish a
> >> Project Management Committee charged with the creation and maintenance
> of
> >> open-source software, for distribution at no charge to the public,
> related
> >> to a distributed data integration framework that simplifies common
> aspects
> >> of big data integration such as data ingestion, replication,
> organization
> >> and lifecycle management for both streaming and batch data ecosystems.
> >> >
> >> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Pinot Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >> >
> >> > RESOLVED, that the Apache Pinot Project be and hereby is responsible
> >> for the creation and maintenance of software related to distributed OLAP
> >> data store to provide Real-time Analytics to power wide variety of
> >> analytical use case; and be it further
> >> >
> >> > RESOLVED, that the office of "Vice President, Apache Pinot" be and
> >> hereby is created, the person holding such office to serve at the
> direction
> >> of the Board of Directors as the chair of the Apache Pinot Project, and
> to
> >> have primary responsibility for management of the projects within the
> scope
> >> of responsibility of the Apache Pinot Project; and be it further
> >> >
> >> > RESOLVED, that the persons listed immediately below be and hereby are
> >> appointed to serve as the initial members of the Apache Pinot Project:
> >> > Felix Cheung mailto:felixche...@apache.org>>
> >>

Re: [DISCUSS] Apache AGE Sub Project - Visualization Tool

[Felix Cheung]

Sounds great. Is this already built? If it is, it is a software donation
(software grant process)


On Thu, Jun 10, 2021 at 2:11 PM Eya Badal  wrote:

> Dear Everyone,
> @All Mentors
>
> I hope you are doing great.
>
> We would like to discuss the possibility of having a sub-project for
> Apache AGE. This sub-project is a visualization tool that enables Apache
> AGE users to visualize their data.
>
> This tool is a web-based graph visualization tool that allows you to
> visualize a graph. It connects to a Postgres server running the AGE graph
> database extension. AGViewer has a query editor where you can submit SQL
> and Cypher (or Hybrid) queries, allowing you to build, modify and query
> graphs in AGE. The visualization supports many layout formats such as
> COSE-Bilkent, Dagre, and Euler. In addition, there is a table output for
> displaying non-graph results.
>
>
> Please advise and give us your feedback.
>
> Thank you very much,
> Eya Badal
>

Re: Post-release of Sedona Python 1.0.1?

[Felix Cheung]

You can’t skip the release vote process but you can make the vote a lot
easier / cleaner if the only diff / commit is the one line change.

We can a quick role in dev@ and once there is 3 votes (like today) we bring
it to IPMC for 72hr. Hopefully it’s not too bad.

Unfortunately you will need to publish the Java artifacts though because
they go together in the same repo.

In some projects they have several repo that makes it easier to change one
codebase vs another.


In this specific case you can also fix this in
https://github.com/apache/incubator-sedona/blob/master/python/setup.py and
just tell people to install with pip from there (git repo), to workaround.
Python people are generally very flexible so I don’t personally think this
issue is a major problem.



On Tue, May 25, 2021 at 10:35 PM Jia Yu  wrote:

> And, this post-release will not change any Sedona Python source code. The
> only place we need to change is the Spark version in "setup.py" which is
> used for publishing the Python package.
>
> On Tue, May 25, 2021 at 10:30 PM Jia Yu  wrote:
>
>> Hi Felix (CCed Pawel),
>>
>> A user immediately reported an issue in Sedona Python 1.0.1. The Python
>> release was misconfigured to only allow PySpark < 3.1.0 [1]
>>
>> This will automatically uninstall PySpark 3.1.1 and re-install PySpark
>> 3.0.2 on the user's local machine. While the user could re-install PySpark
>> 3.1.1 back afterward, this behavior is kind of not good.
>>
>> I wonder if we can release Sedona 1.0.1 post-release on PyPi without
>> going through the voting process [2]. E.g., 1.0.1-post1. The post-release
>> "post1" probably will not even appear on Pypi.org.
>>
>> [1]
>> https://github.com/apache/incubator-sedona/blob/master/python/setup.py#L39
>> [2] https://www.python.org/dev/peps/pep-0440/#post-releases
>>
>> Thanks,
>> Jia
>>
>

Re: [VOTE] Release Apache Sedona 1.0.1-incubating RC1

[Felix Cheung]

+1 (binding) carry over from dev@


On Sat, May 22, 2021 at 1:17 PM Jia Yu  wrote:

> Dear all,
>
> I would like to start a vote for Apache Sedona 1.0.1-incubating RC1
>
> Sedona community vote thread:
>
> https://lists.apache.org/thread.html/ra5f27cd5c9c3608205220c5d12a141c64681b7a5962785ce80fa73ec%40%3Cdev.sedona.apache.org%3E
>
> Sedona community vote result thread:
>
> https://lists.apache.org/thread.html/r7f2b0e72296a6fc10735148b05fa6a5d256ff7a24110c3b4920b2ef3%40%3Cdev.sedona.apache.org%3E
>
> Release notes:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/release-notes.md
>
> Build instructions:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/compile.md
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.1-incubating-rc1
>
> GPG public key to verify the Release:
> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.1-incubating-rc1/
>
> The vote will be open for at least 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
>
> Thanks,
> Jia Yu
>

Re: [VOTE] Release Apache Sedona 1.0.1-incubating-rc1

[Felix Cheung]

+1

Great

On Fri, May 21, 2021 at 12:49 AM Jia Yu  wrote:

> Hi Felix,
>
> Thanks for your time!
>
> 1. Actually the build instruction is already in the source.tar.gz because
> the build instruction is by default delivered together with the source
> code. And it is also git tagged together with the source code. Please see
> 1.0.1-rc1 git tag:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/compile.md
>
> 2. All java artifacts had been staged on ASF maven repo when I created this
> vote email.
>
> 3. docs/archive is for the old GeoSpark docs. We keep it in the doc website
> for users who are still using GeoSpark, instead of Sedona. The generated
> docs are put here: http://sedona.apache.org/archive/download/overview/
>
> Thanks,
> Jia
>
>
> On Thu, May 20, 2021 at 10:50 AM Felix Cheung 
> wrote:
>
> > 1. You probably shouldn't put .md doc on release share - if I understand
> > the suggestion is to include it into the src.tar.gz (and into the source
> > repo) so that they are git tagged and packaged together
> >
> > 2. Do you have java artifacts that should be staged?
> >
> > 3. checklist
> > incubating in name
> > signature and hash fine
> > DISCLAIMER is fine
> > LICENSE and NOTICE are fine
> > No unexpected binary files
> > All source have ASF headers
> >
> > 4. what is /docs/archive for?
> >
> >
> > On Wed, May 19, 2021 at 2:41 PM Adam Binford  wrote:
> >
> > > +1 (non-binding)
> > >
> > > On Wed, May 19, 2021 at 12:58 AM Jia Yu  wrote:
> > >
> > > > Hi all,
> > > >
> > > > This is a call for vote on Apache Sedona 1.0.1-incubating-rc1. Please
> > > refer
> > > > to the changes listed at the bottom of this email.
> > > >
> > > > Release notes:
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/release-notes.md
> > > >
> > > > Build instructions:
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/compile.md
> > > >
> > > > GitHub tag:
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.1-incubating-rc1
> > > >
> > > > GPG public key to verify the Release:
> > > > https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
> > > >
> > > > Source code and binaries:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.1-incubating-rc1/
> > > >
> > > > The vote will be open for at least 72 hours or until a majority of at
> > > least
> > > > 3 +1 PMC votes are cast
> > > >
> > > > Please vote accordingly:
> > > >
> > > > [ ] +1 approve
> > > >
> > > > [ ] +0 no opinion
> > > >
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > Checklist for reference (because of DISCLAIMER-WIP, other checklist
> > items
> > > > are not blockers):
> > > >
> > > > [ ] Download links are valid.
> > > >
> > > > [ ] Checksums and PGP signatures are valid.
> > > >
> > > > [ ] DISCLAIMER is included.
> > > >
> > > > [ ] Source code artifacts have correct names matching the current
> > > release.
> > > >
> > > > For a detailed checklist  please refer to:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > > >
> > > > 
> > > > Changes according to the comments of Justin Mclean on the
> > > 1.0.0-incubating
> > > > release
> > > > Original comment URL:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r828873cbb2685dcfb0719680f3aac6dbf982720fcd9cd5f69a26ec55%40%3Cgeneral.incubator.apache.org%3E
> > > >
> > > > 1. There are some test files I think I like to know where they come
> > from
> > > > e.g. county_small_wkb.tsv and what license the contents are under.
> > > >
> > > > License for test data has been added to Sedona license
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/LICENSE
> > > >
> > > > 2. The LICENSE here seems odd why does it have "Copyright (c)
> > 2019-2020,
> > > > Apache Sedona” in it?
> > > >
> > > > The issue has been fixed. The license for zeppelin plugin has been
> > added
> > > to
> > > > LICENSE as well.
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/LICENSE
> > > >
> > > > 3. Please put instructions on how to build in the release,
> instructions
> > > can
> > > > change over time so pointing to a URL may not be helpful when trying
> to
> > > > build older versions.
> > > >
> > > > Build instruction has been added to svn/dist/dev
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.1-incubating-rc1/
> > > >
> > >
> > >
> > > --
> > > Adam Binford
> > >
> >
>

Re: [VOTE] Release Apache Sedona 1.0.1-incubating-rc1

[Felix Cheung]

1. You probably shouldn't put .md doc on release share - if I understand
the suggestion is to include it into the src.tar.gz (and into the source
repo) so that they are git tagged and packaged together

2. Do you have java artifacts that should be staged?

3. checklist
incubating in name
signature and hash fine
DISCLAIMER is fine
LICENSE and NOTICE are fine
No unexpected binary files
All source have ASF headers

4. what is /docs/archive for?


On Wed, May 19, 2021 at 2:41 PM Adam Binford  wrote:

> +1 (non-binding)
>
> On Wed, May 19, 2021 at 12:58 AM Jia Yu  wrote:
>
> > Hi all,
> >
> > This is a call for vote on Apache Sedona 1.0.1-incubating-rc1. Please
> refer
> > to the changes listed at the bottom of this email.
> >
> > Release notes:
> >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/release-notes.md
> >
> > Build instructions:
> >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/compile.md
> >
> > GitHub tag:
> >
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.1-incubating-rc1
> >
> > GPG public key to verify the Release:
> > https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
> >
> > Source code and binaries:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.1-incubating-rc1/
> >
> > The vote will be open for at least 72 hours or until a majority of at
> least
> > 3 +1 PMC votes are cast
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove with the reason
> >
> > Checklist for reference (because of DISCLAIMER-WIP, other checklist items
> > are not blockers):
> >
> > [ ] Download links are valid.
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> > [ ] DISCLAIMER is included.
> >
> > [ ] Source code artifacts have correct names matching the current
> release.
> >
> > For a detailed checklist  please refer to:
> >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > 
> > Changes according to the comments of Justin Mclean on the
> 1.0.0-incubating
> > release
> > Original comment URL:
> >
> >
> https://lists.apache.org/thread.html/r828873cbb2685dcfb0719680f3aac6dbf982720fcd9cd5f69a26ec55%40%3Cgeneral.incubator.apache.org%3E
> >
> > 1. There are some test files I think I like to know where they come from
> > e.g. county_small_wkb.tsv and what license the contents are under.
> >
> > License for test data has been added to Sedona license
> >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/LICENSE
> >
> > 2. The LICENSE here seems odd why does it have "Copyright (c) 2019-2020,
> > Apache Sedona” in it?
> >
> > The issue has been fixed. The license for zeppelin plugin has been added
> to
> > LICENSE as well.
> >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/LICENSE
> >
> > 3. Please put instructions on how to build in the release, instructions
> can
> > change over time so pointing to a URL may not be helpful when trying to
> > build older versions.
> >
> > Build instruction has been added to svn/dist/dev
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.1-incubating-rc1/
> >
>
>
> --
> Adam Binford
>

Re: Review request for Apache Maturity Model Assessment for Pinot

[Felix Cheung]

Great!


From: Seunghyun Lee 
Sent: Monday, May 17, 2021 5:08:42 PM
To: dev@pinot.apache.org 
Subject: Review request for Apache Maturity Model Assessment for Pinot

Hi all,

I have finished the initial draft of Apache Maturity Model Assessment
document for Pinot. This document will be evaluated as part of our
graduation process.

https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot

It would be great if we can get some reviews from the community.

Best,
Seunghyun

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Upcoming Sedona talk

[Felix Cheung]

https://databricks.com/session_na21/large-scale-geospatial-indexing-and-analysis-on-apache-spark

I will be talking about Sedona (which we use!)

Re: DISCUSS Pinot Graduation

[Felix Cheung]

Agreed it is not a blocker per se, but I figure it will raise some questions if 
more board/podling reports are missed.

Maybe worthwhile to setup forwarding from dev@ to slack.



From: kishore g 
Sent: Saturday, May 15, 2021 6:53 PM
To: dev@pinot.apache.org
Cc: Mayank Shrivastava; j...@apache.org; ol...@apache.org
Subject: Re: DISCUSS Pinot Graduation

I agree with you on traffic on dev. We tried to move few discussions to dev@ 
but entire community is active on the slack channel and prefer discussion on 
GitHub issues. We push everything to dev@ so folks on ML have all the 
information.

We have < 100 on @dev vs ~1300 on slack. Trying to push slack members to join 
dev did not work in the past and I doubt it will work now. We will continue to 
make sure all discussions on slack are sent as digest to dev.

We have mentioned this in our reports last year and we did not hear any 
objections from the board.


Thanks,
Kishore G

On Fri, May 14, 2021 at 8:38 PM Felix Cheung 
mailto:felixche...@apache.org>> wrote:
Generally it looks good, I’ve checked clutch report, website checks etc, but a 
few reminders and areas to pay attention to:

- dev@ traffic is very or almost zero? I realize the community is active on 
slack and summary is sent to dev@ everyday, but some traffic there will be 
good...

- ... because people will miss stuff. The podling report reminder was sent 
there and Pinot just missed this month’s podling report. Let’s make sure the 
month is out promptly next month

- pls make sure the incubation status is updated
http://incubator.apache.org/projects/pinot - for instance either the committer 
list is not sorted or the last date is wrong (should not be 2020). The rest of 
the page can use updating too. Also many sections there have placeholder 
content, pls fill them in.

- also as suggested, please take the maturity model, fill it in and share with 
dev@ anything identified - project maturity model (as a guide)
https://community.apache.org/apache-way/apache-project-maturity-model.html



On Fri, May 14, 2021 at 3:13 PM Mayank Shrivastava 
mailto:maya...@apache.org>> wrote:
Mentors - Felix, Olivier, Jim,
Wondering what your thoughts on are for proposing Pinot's graduation. We have 
addressed all the issues that have been brought up in the past. If there are 
other steps to be taken, please let us know and we can also take care of those 
as well. Looking forward to your suggestions and support.

Regards,
Mayank

On Mon, May 10, 2021 at 12:54 PM Fu Xiang 
mailto:fx19880...@gmail.com>> wrote:
+1! Glad to see we've accomplished a lot and the community is pretty strong and 
healthy!

On Mon, May 10, 2021 at 11:23 AM Subbu Subramaniam 
mailto:mcvsu...@apache.org>> wrote:
+1

Let us know how we can help with the graduation, and if there are any pending 
items to be resolved.

-Subbu

On 2021/05/09 14:07:45, kishore g 
mailto:g.kish...@gmail.com>> wrote:
> Hello,
>
>
> I would like to start a conversation about the readiness of Apache Pinot to
> graduate. We have come a long way since we incubated in Apache, with:
>
>
>-
>
>7800+ contributions from 168 contributors
>-
>
>7 releases by various committers
>-
>
>6 new committers invited (all accepted)
>-
>
>Apache website available at: https://pinot.apache.org
>-
>
>Updated Apache Pinot (incubating) page
><https://incubator.apache.org/projects/pinot.html>
>-
>
>Updated Roster Page <https://whimsy.apache.org/roster/ppmc/pinot>
>-
>
>Dev conversations at 
> d...@pinot.incubator.org<mailto:d...@pinot.incubator.org>
>-
>
>Diverse committers and PPMCs (from 7 companies / institutes)
>-
>
>We have built a meritocratic and open collaborative progress (the Apache
>way)
>-
>
>A strong community of 1200+ members in Apache Pinot Slack
><https://communityinviter.com/apps/apache-pinot/apache-pinot>. All
>conversations emailed to dev@ in the form of a digest
>
>
> Please let us know if there are remaining steps involved in completing the
> graduation process.
>
> Thanks,
>
> Kishore G
>

-
To unsubscribe, e-mail: 
dev-unsubscr...@pinot.apache.org<mailto:dev-unsubscr...@pinot.apache.org>
For additional commands, e-mail: 
dev-h...@pinot.apache.org<mailto:dev-h...@pinot.apache.org>



--
Xiang Fu

Re: DISCUSS Pinot Graduation

[Felix Cheung]

Generally it looks good, I’ve checked clutch report, website checks etc,
but a few reminders and areas to pay attention to:

- dev@ traffic is very or almost zero? I realize the community is active on
slack and summary is sent to dev@ everyday, but some traffic there will be
good...

- ... because people will miss stuff. The podling report reminder was sent
there and Pinot just missed this month’s podling report. Let’s make sure
the month is out promptly next month

- pls make sure the incubation status is updated
http://incubator.apache.org/projects/pinot - for instance either the
committer list is not sorted or the last date is wrong (should not be
2020). The rest of the page can use updating too. Also many sections there
have placeholder content, pls fill them in.

- also as suggested, please take the maturity model, fill it in and share
with dev@ anything identified - project maturity model (as a guide)
https://community.apache.org/apache-way/apache-project-maturity-model.html



On Fri, May 14, 2021 at 3:13 PM Mayank Shrivastava 
wrote:

> Mentors - Felix, Olivier, Jim,
> Wondering what your thoughts on are for proposing Pinot's graduation. We
> have addressed all the issues that have been brought up in the past. If
> there are other steps to be taken, please let us know and we can also take
> care of those as well. Looking forward to your suggestions and support.
>
> Regards,
> Mayank
>
> On Mon, May 10, 2021 at 12:54 PM Fu Xiang  wrote:
>
>> +1! Glad to see we've accomplished a lot and the community is pretty
>> strong and healthy!
>>
>> On Mon, May 10, 2021 at 11:23 AM Subbu Subramaniam 
>> wrote:
>>
>>> +1
>>>
>>> Let us know how we can help with the graduation, and if there are any
>>> pending items to be resolved.
>>>
>>> -Subbu
>>>
>>> On 2021/05/09 14:07:45, kishore g  wrote:
>>> > Hello,
>>> >
>>> >
>>> > I would like to start a conversation about the readiness of Apache
>>> Pinot to
>>> > graduate. We have come a long way since we incubated in Apache, with:
>>> >
>>> >
>>> >-
>>> >
>>> >7800+ contributions from 168 contributors
>>> >-
>>> >
>>> >7 releases by various committers
>>> >-
>>> >
>>> >6 new committers invited (all accepted)
>>> >-
>>> >
>>> >Apache website available at: https://pinot.apache.org
>>> >-
>>> >
>>> >Updated Apache Pinot (incubating) page
>>> >
>>> >-
>>> >
>>> >Updated Roster Page 
>>> >-
>>> >
>>> >Dev conversations at d...@pinot.incubator.org
>>> >-
>>> >
>>> >Diverse committers and PPMCs (from 7 companies / institutes)
>>> >-
>>> >
>>> >We have built a meritocratic and open collaborative progress (the
>>> Apache
>>> >way)
>>> >-
>>> >
>>> >A strong community of 1200+ members in Apache Pinot Slack
>>> >. All
>>> >conversations emailed to dev@ in the form of a digest
>>> >
>>> >
>>> > Please let us know if there are remaining steps involved in completing
>>> the
>>> > graduation process.
>>> >
>>> > Thanks,
>>> >
>>> > Kishore G
>>> >
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
>>> For additional commands, e-mail: dev-h...@pinot.apache.org
>>>
>>>
>>
>> --
>> Xiang Fu
>>
>

Re: [MENTORS] Incubator report submitted

[Felix Cheung]

I can sign off Sedona. Will check to update whimsy now


On Thu, May 13, 2021 at 11:57 PM Justin Mclean 
wrote:

> HI,
>
> The report has been submitted.
>
> The Sedona and Spot reports do not have sign-off by mentors, so please
> sign off here [1] before the board meets.
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/board/agenda/2021-05-19/Incubator

Re: Podling Pinot Report Reminder - May 2021

[Felix Cheung]

Reminder


From: jmcl...@apache.org 
Sent: Thursday, April 22, 2021 6:04:08 PM
To: d...@pinot.incubator.apache.org 
Subject: Podling Pinot Report Reminder - May 2021

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, 19 May 2021.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, May 05).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/May2021

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Re: Podling Sedona Report Reminder - May 2021

[Felix Cheung]

Reminder


From: jmcl...@apache.org 
Sent: Thursday, April 22, 2021 6:04:11 PM
To: d...@sedona.incubator.apache.org 
Subject: Podling Sedona Report Reminder - May 2021

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, 19 May 2021.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, May 05).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/May2021

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: [VOTE] Release Apache AGE (incubating) version 0.4.0

[Felix Cheung]

+1

drivers/nodejs/src/index.ts - is there a reason this file does not have Apache 
License header?

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- source files have ASF headers - see note at the top




From: Eya Badal 
Sent: Tuesday, April 13, 2021 12:05:07 PM
To: dev@age.apache.org 
Subject: [VOTE] Release Apache AGE (incubating) version 0.4.0

Dear Apache Community,

Please vote on releasing the following candidate as Apache AGE version 0.4.0

The vote is open now and until April 16th at 12:05 PM PST and passes if a 
majority +1 votes are cast, with a minimum of 3 +1 votes.

[ ] +1 Release this package as Apache AGE 0.4.0
[ ] -1 Do not release this package because ...


To learn more about Apache AGE, please see http://age.apache.org/

*
The git tag to be discussed and voted upon:
https://github.com/apache/incubator-age/releases/tag/0.4.0

The git commit hash:
commit e9add439468ccff3780a392f9cead627fcaecf1e

The release files for 0.4.0, can be found at:
https://dist.apache.org/repos/dist/dev/incubator/age/0.4.0.rc0/

The signatures, files, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/age/

Signatures used for AGE RCs can be found in this file:
https://dist.apache.org/repos/dist/dev/incubator/age/KEYS

The fingerprint of key to sign release artifacts:
FD8B 268F 784A CE10 F201  E63B C063 8775 6375 38D2

For information about the contents of this release, see:
https://github.com/apache/incubator-age/releases/tag/0.4.0

Thank you for your time in advance.

Best regards,
Eya Badal

Re: [VOTE] Release Apache Pinot (incubating) 0.7.1 RC0

[Felix Cheung]

Carry over my vote

+1 binding


On Sat, Apr 10, 2021 at 4:04 PM Fu Xiang  wrote:

> Hi all,
>
> This is a call for a vote to release Apache Pinot (incubating) version
> 0.7.1.
>
> Apache Pinot (incubating) is a distributed columnar storage engine that can
> ingest data in realtime and serve analytical queries at low latency.
>
> Pinot community has voted and approved this release.
>
> Vote threads:
>
> https://lists.apache.org/thread.html/rf3737f7739a085fd17120807ea41dfe501137ff26ccc6fa40f96ae4a%40%3Cdev.pinot.apache.org%3E
>
> Result thread:
>
> https://lists.apache.org/thread.html/ra630b726e8a8e2a449555d75cfbe876a7b04a9f10880ea1ea5bb%40%3Cdev.pinot.apache.org%3E
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-
> incubating-0.7.1-rc0/
> 
>
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.7.1-rc0
>
> Git hash for this release:
> *e22be7c3a39e840321d3658e7505f21768b228d6*
>
> The artifacts have been signed with key: *CDEDB21B862F6C66*, which can be
> found in the following KEYS file.
> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
>
> Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.7.1-rc0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1025
>
> Documentation on verifying a release candidate:
> https://cwiki.apache.org/confluence/display/PINOT
> /Validating+a+release+candidate
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly,
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
>
> Apache Pinot (incubating) team
>

Re: [VOTE] Apache Pinot (incubating) 0.7.1 RC0

[Felix Cheung]

+1

-incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers



From: Chinmay Soman 
Sent: Thursday, April 8, 2021 8:49:40 PM
To: Daniel Lavoie 
Cc: dev@pinot.apache.org 
Subject: Re: [VOTE] Apache Pinot (incubating) 0.7.1 RC0

+1

On Thu, Apr 8, 2021 at 4:18 PM Chinmay Soman 
mailto:chinmay.cere...@gmail.com>> wrote:
Yes, never mind its my jdk version - switching to 8. Sorry for the noise.

On Thu, Apr 8, 2021 at 4:15 PM Daniel Lavoie 
mailto:dlav...@live.ca>> wrote:
The maven jococo plugin needs a bump to 0.8.6 if you are running with JDK > 8.

I would recommend switching to Java 8 for your local build.

On Apr 8, 2021, at 7:12 PM, Chinmay Soman 
mailto:chinmay.cere...@gmail.com>> wrote:

I'm not sure if its just my environment, but seeing some build failures:

[ERROR] Exception in thread "main" java.lang.reflect.InvocationTargetException
[ERROR] at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[ERROR] at 
java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
[ERROR] at 
java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
[ERROR] Caused by: java.lang.RuntimeException: Class java/util/UUID could not 
be instrumented.
[ERROR] at 
org.jacoco.agent.rt.internal_6da5971.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140)
[ERROR] at 
org.jacoco.agent.rt.internal_6da5971.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101)
[ERROR] at 
org.jacoco.agent.rt.internal_6da5971.PreMain.createRuntime(PreMain.java:55)
[ERROR] at org.jacoco.agent.rt.internal_6da5971.PreMain.premain(PreMain.java:47)
[ERROR] ... 6 more
[ERROR] Caused by: java.lang.NoSuchFieldException: $jacocoAccess
[ERROR] at java.base/java.lang.Class.getField(Class.java:2013)
[ERROR] at 
org.jacoco.agent.rt.internal_6da5971.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138)
[ERROR] ... 9 more
[ERROR] *** java.lang.instrument ASSERTION FAILED ***: "result" with message 
agent load/premain call failed at 
./src/java.instrument/share/native/libinstrument/JPLISAgent.c line: 422
[ERROR] /bin/sh: line 1: 21674 Abort trap: 6   
/usr/local/Cellar/openjdk/14.0.1/libexec/openjdk.jdk/Contents/Home/bin/java 
-javaagent:/Users/chinmaysoman/.m2/repository/org/jacoco/org.jacoco.agent/0.7.7.201606060606/org.jacoco.agent-0.7.7.201606060606-runtime.jar=destfile=/Users/chinmaysoman/projects/rc-test/rc-test/apache-pinot-incubating-0.7.1-src/pinot-spi/target/jacoco.exec
 -Xms4g -Xmx4g -jar 
/Users/chinmaysoman/projects/rc-test/rc-test/apache-pinot-incubating-0.7.1-src/pinot-spi/target/surefire/surefirebooter10242600033471299580.jar
 
/Users/chinmaysoman/projects/rc-test/rc-test/apache-pinot-incubating-0.7.1-src/pinot-spi/target/surefire
 2021-04-08T16-12-03_030-jvmRun1 surefire15948155137112062866tmp 
surefire_02116322378581512756tmp

On Thu, Apr 8, 2021 at 3:14 PM Mayank Shrivastava 
mailto:maya...@apache.org>> wrote:
+1

On Wed, Apr 7, 2021 at 3:09 PM Xiaotian Jiang 
mailto:jackie@gmail.com>> wrote:
+1

On Wed, Apr 7, 2021 at 2:56 PM Fu Xiang 
mailto:fx19880...@gmail.com>> wrote:
Hi Pinot Community,

This is a call for a vote to release Apache Pinot (incubating) version 0.7.1.

The release candidate:
https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.1-rc0/

Git tag for this release:
https://github.com/apache/incubator-pinot/tree/release-0.7.1-rc0

Git hash for this release:
e22be7c3a39e840321d3658e7505f21768b228d6

The artifacts have been signed with key: CDEDB21B862F6C66, which can be found 
in the following KEYS file.

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.10.0

[Felix Cheung]

+1 binding

- LICENSE and NOTICE are fine
you should include year 2021 in NOTICE

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- No unexpected binary files
- All source files have ASF headers


On Wed, Apr 7, 2021 at 7:37 AM Kris Calvin  wrote:

> +1 (non-binding)
> I checked:
> -Digital signature and hashes correct
> -DISCLAIMER  file exists
> -The name of the published file contains “incubating"
> -LICENSE and NOTICE files exists
> -The NOTICE year does not seem to be updated (please note).
>
> Jason Lowe  于2021年4月7日周三 下午10:07写道：
>
> > Echoing my +1 from the vote on the YuniKorn dev list.
> >
> > Jason
> >
> > On Mon, Apr 5, 2021 at 8:59 PM Tao Yang  wrote:
> >
> > > Hello IPMC
> > >
> > > The Apache YuniKorn community has voted and approved the release Apache
> > > YuniKorn (incubating) 0.10.0. We now kindly request the IPMC members
> > review
> > > and vote for this release.
> > >
> > > YuniKorn is a standalone, universal resource scheduler that can support
> > > both long-running and batch workloads. The current release provides
> some
> > > enhanced functions, including gang-scheduling support, application
> > > lifecycle control, improvements on web UI and web-site, etc.
> > >
> > > YuniKorn community vote thread:
> > >
> > >
> >
> https://lists.apache.org/thread.html/rfbb34a8facfeecebdbd4ca17a65556166e522b029190520915915661%40%3Cdev.yunikorn.apache.org%3E
> > >
> > > Vote result thread:
> > >
> > >
> >
> https://lists.apache.org/thread.html/re18dbfd2be3a5d11c1e25fa86b3b111ea4e802e00119da81df35a7df%40%3Cdev.yunikorn.apache.org%3E
> > >
> > > Issues included in this release:
> > > https://issues.apache.org/jira/projects/YUNIKORN/versions/12348351
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.10.0/
> > >
> > > This release has been signed with a PGP available here:
> > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS
> > >
> > > Git tag for the release:
> > >   - https://github.com/apache/incubator-yunikorn-core/tree/v0.10.0
> > >   - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.10.0
> > >   -
> > >
> > >
> >
> https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.10.0
> > >   - https://github.com/apache/incubator-yunikorn-web/tree/v0.10.0
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> > > of votes is reached.
> > >
> > > Please vote accordingly:
> > > [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.10.0
> > > [ ] +0
> > > [ ] -1 Do not approve (please specify the reason)
> > >
> > > Thanks,
> > > Tao Yang
> > > Apache YuniKorn (Incubating)
> > >
> >
>
>
> --
> Best  wishes！
> CalvinKirs
>

Re: Welcoming six new Apache Spark committers

[Felix Cheung]

Welcome!


From: Driesprong, Fokko 
Sent: Friday, March 26, 2021 1:25:33 PM
To: Matei Zaharia 
Cc: Spark Dev List 
Subject: Re: Welcoming six new Apache Spark committers

Well deserved all! Welcome!

Op vr 26 mrt. 2021 om 21:21 schreef Matei Zaharia 
mailto:matei.zaha...@gmail.com>>
Hi all,

The Spark PMC recently voted to add several new committers. Please join me in 
welcoming them to their new role! Our new committers are:

- Maciej Szymkiewicz (contributor to PySpark)
- Max Gekk (contributor to Spark SQL)
- Kent Yao (contributor to Spark SQL)
- Attila Zsolt Piros (contributor to decommissioning and Spark on Kubernetes)
- Yi Wu (contributor to Spark Core and SQL)
- Gabor Somogyi (contributor to Streaming and security)

All six of them contributed to Spark 3.1 and we’re very excited to have them 
join as committers.

Matei and the Spark PMC
-
To unsubscribe e-mail: 
dev-unsubscr...@spark.apache.org

Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1

[Felix Cheung]

For some reason the git hash has changed in release git tag

https://github.com/apache/incubator-pinot/commits/release-0.7.0

https://github.com/apache/incubator-pinot/commit/de0236c25727ffc2408c5bf55836bbfecf40499c




On Fri, Mar 19, 2021 at 11:00 AM kishore g  wrote:

> Jim/Felix and others
>
> Do we have your +1 to go ahead with the release.
>
> Thanks
> Kishore G
>
> On Thu, Mar 18, 2021 at 9:32 PM kishore g  wrote:
>
> > That would be great. We will update the release runbook to make sure this
> > doesn't happen again.
> >
> > Here is my +1
> >
> >
> >
> > On Thu, Mar 18, 2021 at 11:03 AM Jim Jagielski  wrote:
> >
> >> I propose that we run the vote anyway, thus ensuring IPMC oversight and
> >> (post)approval, and then update the release runbook to make sure this
> >> doesn't happen again. Make sense?
> >>
> >> > On Mar 17, 2021, at 11:35 PM, Felix Cheung 
> >> wrote:
> >> >
> >> > It is unclear the guidance on this but since it is impossible remove
> >> from
> >> > maven
> >> >
> >> > https://repository.apache.org/#nexus-search;classname~Pinot
> >> >
> >> > Once it is published, I’d suggest we update all the links and git hash
> >> and
> >> > still proceed to vote on this. If there is any issue we should vote on
> >> > another release with fix ASAP. Otherwise hopefully IPMC can continue
> to
> >> > sign off on this release.
> >> >
> >> >
> >> >
> >> > On Wed, Mar 17, 2021 at 3:09 PM kishore g 
> wrote:
> >> >
> >> >> Apologies for the mistake. We have done multiple releases until now
> and
> >> >> this is the first time we missed the step to get the approval from
> >> IPMC was
> >> >> missed before making the release.
> >> >>
> >> >> What is the right thing to do at this point? Should we cut another
> >> release
> >> >> or can we go ahead with this and ensure that this does not happen
> >> again.
> >> >>
> >> >> thanks,
> >> >> Kishore G
> >> >>
> >> >> On Wed, Mar 17, 2021 at 10:59 AM Felix Cheung <
> felixche...@apache.org>
> >> >> wrote:
> >> >>
> >> >>> Unfortunately this isn’t the right process for a podling release.
> >> >>>
> >> >>> As the mentor, I am sorry to see the release is not up to the
> standard
> >> >>> upheld by previous releases.
> >> >>>
> >> >>>
> >> >>> On Wed, Mar 17, 2021 at 7:02 AM kezhenxu94@apache <
> >> kezhenx...@apache.org
> >> >>>
> >> >>> wrote:
> >> >>>
> >> >>>> I think this release violates the Apache release policy because it
> >> >> didn’t
> >> >>>> get the approvals from IPMC but was released actually (in both
> >> dist.a.o
> >> >>> and
> >> >>>> GitHub).
> >> >>>>
> >> >>>> —
> >> >>>> Zhenxu Ke (柯振旭)
> >> >>>> GitHub @kezhenxu94
> >> >>>>
> >> >>>>> On Mar 17, 2021, at 06:14, Yupeng Fu  wrote:
> >> >>>>>
> >> >>>>> Hi all,
> >> >>>>>
> >> >>>>> This is a call for vote to the release Apache Pinot (incubating)
> >> >>> version
> >> >>>>> 0.7.0.
> >> >>>>>
> >> >>>>> Apache Pinot (incubating) is a distributed columnar storage engine
> >> >> that
> >> >>>> can
> >> >>>>> ingest data in realtime and serve analytical queries at low
> latency.
> >> >>>>>
> >> >>>>> Pinot community has voted and approved this release.
> >> >>>>>
> >> >>>>> Vote thread:
> >> >>>>>
> >> >>>>
> >> >>>
> >> >>
> >>
> https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E
> >> >>>>>
> >> >>>>>
> >> >>>>> Result thread:
> >> >>>>>
> >> >>>>
> >> >>>

Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1

[Felix Cheung]

It is unclear the guidance on this but since it is impossible remove from
maven

https://repository.apache.org/#nexus-search;classname~Pinot

Once it is published, I’d suggest we update all the links and git hash and
still proceed to vote on this. If there is any issue we should vote on
another release with fix ASAP. Otherwise hopefully IPMC can continue to
sign off on this release.



On Wed, Mar 17, 2021 at 3:09 PM kishore g  wrote:

> Apologies for the mistake. We have done multiple releases until now and
> this is the first time we missed the step to get the approval from IPMC was
> missed before making the release.
>
> What is the right thing to do at this point? Should we cut another release
> or can we go ahead with this and ensure that this does not happen again.
>
> thanks,
> Kishore G
>
> On Wed, Mar 17, 2021 at 10:59 AM Felix Cheung 
> wrote:
>
> > Unfortunately this isn’t the right process for a podling release.
> >
> > As the mentor, I am sorry to see the release is not up to the standard
> > upheld by previous releases.
> >
> >
> > On Wed, Mar 17, 2021 at 7:02 AM kezhenxu94@apache  >
> > wrote:
> >
> > > I think this release violates the Apache release policy because it
> didn’t
> > > get the approvals from IPMC but was released actually (in both dist.a.o
> > and
> > > GitHub).
> > >
> > > —
> > > Zhenxu Ke (柯振旭)
> > > GitHub @kezhenxu94
> > >
> > > > On Mar 17, 2021, at 06:14, Yupeng Fu  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > This is a call for vote to the release Apache Pinot (incubating)
> > version
> > > > 0.7.0.
> > > >
> > > > Apache Pinot (incubating) is a distributed columnar storage engine
> that
> > > can
> > > > ingest data in realtime and serve analytical queries at low latency.
> > > >
> > > > Pinot community has voted and approved this release.
> > > >
> > > > Vote thread:
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E
> > > >
> > > >
> > > > Result thread:
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r80672ac39a6a6eb7f63c7dbbf595de2f7350cf75d2a7a598601da638%40%3Cdev.pinot.apache.org%3E
> > > >
> > > > The release candidate:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/
> > > >
> > > >
> > > > Git tag for this release:
> > > > <https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc0>
> > > > https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
> > > >
> > > > Git hash for this release:
> > > > 695ca390a8080409b3b76f250f2315b81b86b362
> > > >
> > > > The artifacts have been signed with key: F41AB2B856C6C29D, which can
> be
> > > > found in the following KEYS file.
> > > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> > > >
> > > > Release notes:
> > > >
> > https://github.com/apache/incubator-pinot/releases/tag/release-0.7.0-rc1
> > > >
> > > > Staging repository:
> > > > <
> > https://repository.apache.org/content/repositories/orgapachepinot-1023>
> > > >
> https://repository.apache.org/content/repositories/orgapachepinot-1024
> > > >
> > > > Documentation on verifying a release candidate:
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> > > >
> > > >
> > > > The vote will be open for at least 72 hours or until the necessary
> > > number of
> > > > votes are reached.
> > > >
> > > > Please vote accordingly,
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > Thanks,
> > > > Apache Pinot (incubating) team
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1

[Felix Cheung]

Unfortunately this isn’t the right process for a podling release.

As the mentor, I am sorry to see the release is not up to the standard
upheld by previous releases.


On Wed, Mar 17, 2021 at 7:02 AM kezhenxu94@apache 
wrote:

> I think this release violates the Apache release policy because it didn’t
> get the approvals from IPMC but was released actually (in both dist.a.o and
> GitHub).
>
> —
> Zhenxu Ke (柯振旭)
> GitHub @kezhenxu94
>
> > On Mar 17, 2021, at 06:14, Yupeng Fu  wrote:
> >
> > Hi all,
> >
> > This is a call for vote to the release Apache Pinot (incubating) version
> > 0.7.0.
> >
> > Apache Pinot (incubating) is a distributed columnar storage engine that
> can
> > ingest data in realtime and serve analytical queries at low latency.
> >
> > Pinot community has voted and approved this release.
> >
> > Vote thread:
> >
> https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E
> >
> >
> > Result thread:
> >
> https://lists.apache.org/thread.html/r80672ac39a6a6eb7f63c7dbbf595de2f7350cf75d2a7a598601da638%40%3Cdev.pinot.apache.org%3E
> >
> > The release candidate:
> >
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/
> >
> >
> > Git tag for this release:
> > 
> > https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
> >
> > Git hash for this release:
> > 695ca390a8080409b3b76f250f2315b81b86b362
> >
> > The artifacts have been signed with key: F41AB2B856C6C29D, which can be
> > found in the following KEYS file.
> > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> >
> > Release notes:
> > https://github.com/apache/incubator-pinot/releases/tag/release-0.7.0-rc1
> >
> > Staging repository:
> > 
> > https://repository.apache.org/content/repositories/orgapachepinot-1024
> >
> > Documentation on verifying a release candidate:
> >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> >
> >
> > The vote will be open for at least 72 hours or until the necessary
> number of
> > votes are reached.
> >
> > Please vote accordingly,
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > Apache Pinot (incubating) team
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] AGE Container Support

[Felix Cheung]

I’d like to point out the while it is convenient, as per policy, an Apache 
project should not have “official” or dev binaries that created nightly or 
similarly that is not an approved, voted release.

In other words, dev tag on development branch should be clearly marked as not 
an official release

https://www.apache.org/legal/release-policy.html#host-rc



From: Nicholas Sorrell 
Sent: Tuesday, March 9, 2021 6:07:32 AM
To: dev@age.apache.org 
Subject: Re: [DISCUSS] AGE Container Support

Because Docker builds can support multiple tags, I would propose that the 
default `latest` tag point to the latest stable release and that version 
tagging becomes explicit (i.e., 0.3.0) in the future AGE Docker images. I would 
also propose a `dev` tag that points to the head of the chosen development 
branch.

Regarding if the containers should include Postgres, I would say yes. I think 
the main goal of the containers is to make it easy to use/try/contribute-to 
AGE, and as long as the Docker Hub images are automated, the Dockerfile will be 
viewable by users who want to learn how they can include the extension into 
their own custom build of PG (such as TimeScale). For example, anyone looking 
for dependencies and build steps could look at 
https://hub.docker.com/r/sorrell/agensgraph-extension/dockerfile.

When it comes to virtualization, I think including PG is good. As AGE matures, 
the team should look to support binary releases and utilize package management 
(apt/debs, yum/rpms) so that it's easier to install AGE without compiling.

--
Nick Sorrell



From: Eya Badal 
Sent: Monday, March 8, 2021 2:27 PM
To: dev@age.apache.org 
Subject: Re: [DISCUSS] AGE Container Support



On 2021/02/18 22:24:04, Josh Innis  wrote:
> Hi All,
>
> The AGE community is asking us to support more containers than just Docker,
> see https://github.com/apache/incubator-age/issues/24. Additionally, upon
> review of our Docker images they are in need of being updated.
>
> The Docker images still refer to AgensGraph-Extension. This is due to these
> images being set up before our official acceptance to the Apache incubator
> and the official name change to Apache AGE (A Graph Extension).
> Furthermore, these images refer to the master branch of AGE, so these are
> pointing to development work instead of any official release. Personally, I
> believe that should be altered, but please let us know what you think.
>
> Moving on to the github issue: Some of our community is unable to use
> Docker and is requesting us to support LXC/Snap and/or Kata. For a brief
> summary of all these technologies, please refer to the links below.
>
> LXC:
> https://linuxcontainers.org/lxc/introduction/
>
> Snap:
> https://snapcraft.io/about
>
> A forum discussing Snap:
> https://askubuntu.com/questions/808524/whats-the-main-difference-between-docker-and-snap
>
> Kata Official Site:
> https://katacontainers.io/
>
> A Good Discussion on Kata:
> https://platform9.com/blog/kata-containers-docker-and-kubernetes-how-they-all-fit-together/
>
> Personally, some of the questions I have on the subject before going
> forward on providing support for this is: AGE is an extension of Postgres,
> so should our containers include Postgres in them to avoid dependencies.
> Furthermore, would that affect users' ability to use other extensions, such
> as TimeScaleDB, in these environments?
>
> Thanks.
>
>We requested to have a space on Apache docker hub. Once we have a space on 
>that docker hub we can have official Apache AGE images over there.

Thank you!!

Status from website checks

[Felix Cheung]

https://whimsy.apache.org/pods/project/sedona

Re: [ANNOUNCE] Announcing Apache Spark 3.1.1

[Felix Cheung]

Congrats and thanks!


From: Hyukjin Kwon 
Sent: Wednesday, March 3, 2021 4:09:23 PM
To: Dongjoon Hyun 
Cc: Gabor Somogyi ; Jungtaek Lim 
; angers zhu ; Wenchen Fan 
; Kent Yao ; Takeshi Yamamuro 
; dev ; user @spark 

Subject: Re: [ANNOUNCE] Announcing Apache Spark 3.1.1

Thank you so much guys .. it indeed took a long time and it was pretty tough 
this time :-).
It was all possible because of your guys' support. I sincerely appreciate it .

2021년 3월 4일 (목) 오전 2:26, Dongjoon Hyun 
mailto:dongjoon.h...@gmail.com>>님이 작성:
It took a long time. Thank you, Hyukjin and all!

Bests,
Dongjoon.

On Wed, Mar 3, 2021 at 3:23 AM Gabor Somogyi 
mailto:gabor.g.somo...@gmail.com>> wrote:
Good to hear and great work Hyukjin! 

On Wed, 3 Mar 2021, 11:15 Jungtaek Lim, 
mailto:kabhwan.opensou...@gmail.com>> wrote:
Thanks Hyukjin for driving the huge release, and thanks everyone for 
contributing the release!

On Wed, Mar 3, 2021 at 6:54 PM angers zhu 
mailto:angers@gmail.com>> wrote:
Great work, Hyukjin !

Bests,
Angers

Wenchen Fan mailto:cloud0...@gmail.com>> 于2021年3月3日周三 
下午5:02写道：
Great work and congrats!

On Wed, Mar 3, 2021 at 3:51 PM Kent Yao 
mailto:yaooq...@qq.com>> wrote:
Congrats, all!

Bests,
Kent Yao
@ Data Science Center, Hangzhou Research Institute, NetEase Corp.
a spark enthusiast
kyuubiis a unified multi-tenant JDBC 
interface for large-scale data processing and analytics, built on top of Apache 
Spark.
spark-authorizerA Spark SQL 
extension which provides SQL Standard Authorization for Apache 
Spark.
spark-postgres A library for 
reading data from and transferring data to Postgres / Greenplum with Spark SQL 
and DataFrames, 10~100x faster.
spark-func-extrasA library that 
brings excellent and useful functions from various modern database management 
systems to Apache Spark.



On 03/3/2021 15:11，Takeshi 
Yamamuro wrote：
Great work and Congrats, all!

Bests,
Takeshi

On Wed, Mar 3, 2021 at 2:18 PM Mridul Muralidharan 
mailto:mri...@gmail.com>> wrote:

Thanks Hyukjin and congratulations everyone on the release !

Regards,
Mridul

On Tue, Mar 2, 2021 at 8:54 PM Yuming Wang 
mailto:wgy...@gmail.com>> wrote:
Great work, Hyukjin!

On Wed, Mar 3, 2021 at 9:50 AM Hyukjin Kwon 
mailto:gurwls...@gmail.com>> wrote:
We are excited to announce Spark 3.1.1 today.

Apache Spark 3.1.1 is the second release of the 3.x line. This release adds
Python type annotations and Python dependency management support as part of 
Project Zen.
Other major updates include improved ANSI SQL compliance support, history 
server support
in structured streaming, the general availability (GA) of Kubernetes and node 
decommissioning
in Kubernetes and Standalone. In addition, this release continues to focus on 
usability, stability,
and polish while resolving around 1500 tickets.

We'd like to thank our contributors and users for their contributions and early 
feedback to
this release. This release would not have been possible without you.

To download Spark 3.1.1, head over to the download page:
http://spark.apache.org/downloads.html

To view the release notes:
https://spark.apache.org/releases/spark-release-3-1-1.html



--
---
Takeshi Yamamuro

Re: [ANNOUNCE] Announcing Apache Spark 3.1.1

[Felix Cheung]

Congrats and thanks!


From: Hyukjin Kwon 
Sent: Wednesday, March 3, 2021 4:09:23 PM
To: Dongjoon Hyun 
Cc: Gabor Somogyi ; Jungtaek Lim 
; angers zhu ; Wenchen Fan 
; Kent Yao ; Takeshi Yamamuro 
; dev ; user @spark 

Subject: Re: [ANNOUNCE] Announcing Apache Spark 3.1.1

Thank you so much guys .. it indeed took a long time and it was pretty tough 
this time :-).
It was all possible because of your guys' support. I sincerely appreciate it .

2021년 3월 4일 (목) 오전 2:26, Dongjoon Hyun 
mailto:dongjoon.h...@gmail.com>>님이 작성:
It took a long time. Thank you, Hyukjin and all!

Bests,
Dongjoon.

On Wed, Mar 3, 2021 at 3:23 AM Gabor Somogyi 
mailto:gabor.g.somo...@gmail.com>> wrote:
Good to hear and great work Hyukjin! 

On Wed, 3 Mar 2021, 11:15 Jungtaek Lim, 
mailto:kabhwan.opensou...@gmail.com>> wrote:
Thanks Hyukjin for driving the huge release, and thanks everyone for 
contributing the release!

On Wed, Mar 3, 2021 at 6:54 PM angers zhu 
mailto:angers@gmail.com>> wrote:
Great work, Hyukjin !

Bests,
Angers

Wenchen Fan mailto:cloud0...@gmail.com>> 于2021年3月3日周三 
下午5:02写道：
Great work and congrats!

On Wed, Mar 3, 2021 at 3:51 PM Kent Yao 
mailto:yaooq...@qq.com>> wrote:
Congrats, all!

Bests,
Kent Yao
@ Data Science Center, Hangzhou Research Institute, NetEase Corp.
a spark enthusiast
kyuubiis a unified multi-tenant JDBC 
interface for large-scale data processing and analytics, built on top of Apache 
Spark.
spark-authorizerA Spark SQL 
extension which provides SQL Standard Authorization for Apache 
Spark.
spark-postgres A library for 
reading data from and transferring data to Postgres / Greenplum with Spark SQL 
and DataFrames, 10~100x faster.
spark-func-extrasA library that 
brings excellent and useful functions from various modern database management 
systems to Apache Spark.



On 03/3/2021 15:11，Takeshi 
Yamamuro wrote：
Great work and Congrats, all!

Bests,
Takeshi

On Wed, Mar 3, 2021 at 2:18 PM Mridul Muralidharan 
mailto:mri...@gmail.com>> wrote:

Thanks Hyukjin and congratulations everyone on the release !

Regards,
Mridul

On Tue, Mar 2, 2021 at 8:54 PM Yuming Wang 
mailto:wgy...@gmail.com>> wrote:
Great work, Hyukjin!

On Wed, Mar 3, 2021 at 9:50 AM Hyukjin Kwon 
mailto:gurwls...@gmail.com>> wrote:
We are excited to announce Spark 3.1.1 today.

Apache Spark 3.1.1 is the second release of the 3.x line. This release adds
Python type annotations and Python dependency management support as part of 
Project Zen.
Other major updates include improved ANSI SQL compliance support, history 
server support
in structured streaming, the general availability (GA) of Kubernetes and node 
decommissioning
in Kubernetes and Standalone. In addition, this release continues to focus on 
usability, stability,
and polish while resolving around 1500 tickets.

We'd like to thank our contributors and users for their contributions and early 
feedback to
this release. This release would not have been possible without you.

To download Spark 3.1.1, head over to the download page:
http://spark.apache.org/downloads.html

To view the release notes:
https://spark.apache.org/releases/spark-release-3-1-1.html



--
---
Takeshi Yamamuro

Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC0

[Felix Cheung]

signing key should use a @apache.org address

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE is fine

NOTICE should have year 2021?
Copyright 2018-2020 The Apache Software Foundation
https://www.apache.org/legal/src-headers.html#notice

- No unexpected binary files (some test .gz files)
- All source files have ASF headers



From: Yupeng Fu 
Sent: Friday, March 5, 2021 9:28:24 AM
To: dev@pinot.apache.org 
Subject: [VOTE] Apache Pinot (incubating) 0.7.0 RC0

Hi Pinot Community,

This is a call for vote to the release Apache Pinot (incubating) version
0.7.0.

The release candidate:
https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc0/

Git tag for this release:
https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc0

Git hash for this release:
157bd569303bbab60d79dbd36ba68089d1ee651f

The artifacts have been signed with key: F41AB2B856C6C29D, which can be
found in the following KEYS file.
https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS

Release notes:
https://github.com/apache/incubator-pinot/releases/tag/release-0.7.0-rc0

Staging repository:
https://repository.apache.org/content/repositories/orgapachepinot-1023

Documentation on verifying a release candidate:
https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate


The vote will be open for at least 72 hours or until the necessary number of
votes are reached.

Please vote accordingly,

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
Apache Pinot (incubating) team

--
--Yupeng

Re: [DISCUSS] Put all GeoTools jars into a package on Maven Central

[Felix Cheung]

LGPL is cat X - it wouldn’t be something Apache Sedona should distribute or
depend on
https://www.apache.org/legal/resolved.html#optional


On Thu, Feb 11, 2021 at 11:59 PM Jia Yu  wrote:

> OSGeos LocationTech owns GeoTools. I am thinking whether I should have my
> wrapper on Maven Central to bring those Sedona required GeoTools jars to
> Maven Central. Since it is LGPL, it might be OK to do so.
>
> On Thu, Feb 11, 2021 at 5:18 PM Felix Cheung 
> wrote:
>
> > Who owns or manages GeoTools if it is LGPL?
> >
> > On Thu, Feb 11, 2021 at 12:01 PM Jia Yu  wrote:
> >
> >> Pawel,
> >>
> >> Python-adapter module is always being used by users. But it does not
> come
> >> with GeoTools. To use it, users have to (1) compile the source code of
> >> Python-adapter, or (2) add GeoTools coordiantes from OSGEO repo via
> >> config(""), or (3) download and copy GeoTools jars to SPARK_HOME/jars/
> >>
> >> The easiest is 2, but it looks like it may not work in all environments
> >> since it needs to search OSGEO repo.
> >>
> >> What I am saying is that we can "move" GeoTools jars to Maven Central,
> >> Method 2 will 100% work, users just need to add
> >> "sedona-python-adapter-1.0.0-incubating" and "geotools-24-wrapper-1.0.0"
> >> coordinates in code.
> >>
> >> Do you think this is necessary?
> >>
> >> On Thu, Feb 11, 2021 at 11:40 AM Paweł Kociński <
> >> pawel93kocin...@gmail.com> wrote:
> >>
> >>> Both options seems good to me, but we have to remember that not all of
> >>> Sedona users using cloud solutions, some of them are using Spark with
> >>> hadoop. What about python-adapter module within sedona project, am I
> >>> missing sth ?
> >>> Regards,
> >>> Paweł
> >>>
> >>> czw., 11 lut 2021 o 14:40 Netanel Malka 
> >>> napisał(a):
> >>>
> >>>> I think that we can make it work on Databricks without any changes.
> >>>> After creating a cluster on Databricks, the user can install the
> >>>> geotools packages and provide the osego *(or any other repo)
> >>>> explicitly.*
> >>>>
> >>>> As you can see in the picture:
> >>>>
> >>>> [image: image.png]
> >>>> I can provide the details on how to install it.
> >>>>
> >>>> I think it will solve the problem.
> >>>> What do you think?
> >>>>
> >>>>
> >>>> On Thu, 11 Feb 2021 at 12:24, Jia Yu  wrote:
> >>>>
> >>>>> Hi folks,
> >>>>>
> >>>>> As you can see from the recent discussion in the mailing list
> >>>>> <[Bug][Python] Missing Java class>, in Sedona 1.0.0, because those
> LGPL
> >>>>> GeoTools jars are not on Maven Central (only in OSGEO repo),
> Databricks
> >>>>> cannot get GeoTools jars.
> >>>>>
> >>>>> I believe this will cause lots of trouble to our future Python users.
> >>>>> Reading Shapefiles and do CRS transformation are big selling points
> for
> >>>>> Sedona.
> >>>>>
> >>>>> The easiest way to fix this, without violating ASF policy, is that I
> >>>>> will publish a GeoTools wrapper on Maven Central using the old
> GeoSpark
> >>>>> group ID: https://mvnrepository.com/artifact/org.datasyslab
> >>>>>
> >>>>> For example, org.datasyslab:geotools-24-wrapper:1.0.0
> >>>>>
> >>>>> 1. This GeoTools wrapper does nothing but brings the GeoTools jars
> >>>>> needed by Sedona to Maven Central.
> >>>>> 2. When the Python user calls Sedona, they can add one more
> >>>>> package: org.datasyslab:geotools-24-wrapper:1.0.0
> >>>>>
> >>>>> Another good thing is that: this does not require a new source code
> >>>>> release from Sedona. We only need to update the website and let the
> users
> >>>>> know how to call it.
> >>>>>
> >>>>> Any better ideas?
> >>>>>
> >>>>> Thanks,
> >>>>> Jia
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> Best regards,
> >>>> Netanel Malka.
> >>>>
> >>>
>

Re: [DISCUSS] Put all GeoTools jars into a package on Maven Central

[Felix Cheung]

Who owns or manages GeoTools if it is LGPL?

On Thu, Feb 11, 2021 at 12:01 PM Jia Yu  wrote:

> Pawel,
>
> Python-adapter module is always being used by users. But it does not come
> with GeoTools. To use it, users have to (1) compile the source code of
> Python-adapter, or (2) add GeoTools coordiantes from OSGEO repo via
> config(""), or (3) download and copy GeoTools jars to SPARK_HOME/jars/
>
> The easiest is 2, but it looks like it may not work in all environments
> since it needs to search OSGEO repo.
>
> What I am saying is that we can "move" GeoTools jars to Maven Central,
> Method 2 will 100% work, users just need to add
> "sedona-python-adapter-1.0.0-incubating" and "geotools-24-wrapper-1.0.0"
> coordinates in code.
>
> Do you think this is necessary?
>
> On Thu, Feb 11, 2021 at 11:40 AM Paweł Kociński 
> wrote:
>
>> Both options seems good to me, but we have to remember that not all of
>> Sedona users using cloud solutions, some of them are using Spark with
>> hadoop. What about python-adapter module within sedona project, am I
>> missing sth ?
>> Regards,
>> Paweł
>>
>> czw., 11 lut 2021 o 14:40 Netanel Malka 
>> napisał(a):
>>
>>> I think that we can make it work on Databricks without any changes.
>>> After creating a cluster on Databricks, the user can install the
>>> geotools packages and provide the osego *(or any other repo)
>>> explicitly.*
>>>
>>> As you can see in the picture:
>>>
>>> [image: image.png]
>>> I can provide the details on how to install it.
>>>
>>> I think it will solve the problem.
>>> What do you think?
>>>
>>>
>>> On Thu, 11 Feb 2021 at 12:24, Jia Yu  wrote:
>>>
 Hi folks,

 As you can see from the recent discussion in the mailing list
 <[Bug][Python] Missing Java class>, in Sedona 1.0.0, because those LGPL
 GeoTools jars are not on Maven Central (only in OSGEO repo), Databricks
 cannot get GeoTools jars.

 I believe this will cause lots of trouble to our future Python users.
 Reading Shapefiles and do CRS transformation are big selling points for
 Sedona.

 The easiest way to fix this, without violating ASF policy, is that I
 will publish a GeoTools wrapper on Maven Central using the old GeoSpark
 group ID: https://mvnrepository.com/artifact/org.datasyslab

 For example, org.datasyslab:geotools-24-wrapper:1.0.0

 1. This GeoTools wrapper does nothing but brings the GeoTools jars
 needed by Sedona to Maven Central.
 2. When the Python user calls Sedona, they can add one more
 package: org.datasyslab:geotools-24-wrapper:1.0.0

 Another good thing is that: this does not require a new source code
 release from Sedona. We only need to update the website and let the users
 know how to call it.

 Any better ideas?

 Thanks,
 Jia



>>>
>>> --
>>> Best regards,
>>> Netanel Malka.
>>>
>>

Re: [VOTE] Release Apache Sedona 1.0.0-incubating rc1

[Felix Cheung]

Yes you can call the vote/result : note the comments to follow up in the
next release


On Fri, Feb 5, 2021 at 9:46 PM Jia Yu  wrote:

> Hi Felix,
>
> Can I close the vote now?
>
> Thanks,
> Jia
>
> On Thu, Feb 4, 2021 at 23:33 Juan Pan  wrote:
>
>> Hi,  +1 non-binding.
>>
>>
>> Here is my checking list.
>> [x] Download links are valid.
>> [x] Checksums and PGP signatures are valid.
>> [x] LICENSE, NOTICE and DISCLAIMER-WIP files are correct.
>> [x] Source files have license headers if necessary.
>>
>>
>> A little concern is that
>> The size of  `apache-sedona-1.0.0-incubating-src.tar.gz` exceeds 190M. I
>> suppose it is a big one.
>> After unzipping it, it contains examples and doc, many of which do not
>> have license header.
>> Is it necessary to include these files in the source code tar file?
>>
>>
>>
>>
>>
>>
>> 
>>Juan Pan (Trista)
>>
>> Senior DBA & PMC of Apache ShardingSphere
>> E-mail: panj...@apache.org
>>
>>
>>
>>
>> On 02/4/2021 11:47，Jia Yu wrote：
>> Dear all,
>>
>> We need to collect more votes in order to get this approved. Please take a
>> look at our release when you have time.
>>
>> Thank you very much!
>> Jia
>>
>> On Fri, Jan 29, 2021 at 1:00 PM Felix Cheung 
>> wrote:
>>
>> +1 (binding)
>>
>> Carry from dev@
>>
>>
>> On Thu, Jan 28, 2021 at 10:02 PM Jia Yu  wrote:
>>
>> Dear all,
>>
>> I would like to start a vote for the first release of Apache Sedona
>> 1.0.0-incubating rc1
>>
>> Sedona community vote thread:
>>
>>
>> https://lists.apache.org/thread.html/r1c9406f0ba7b1eb942c03744ebe406344e1cc0bba8ae96430c66f63c%40%3Cdev.sedona.apache.org%3E
>>
>> Sedona community vote result thread:
>>
>>
>> https://lists.apache.org/thread.html/r462bd458b6542ad1bf8994e11717d8924365bfc3bb6282dc6acd5709%40%3Cdev.sedona.apache.org%3E
>>
>> Release note:
>>
>>
>> https://sedona.staged.apache.org/download/GeoSpark-All-Modules-Release-notes/#sedona-100
>>
>> Build instructions:
>> https://sedona.staged.apache.org/download/compile/
>>
>> GitHub tag:
>>
>>
>> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.0-incubating-rc1
>>
>> GPG public key to verify the Release:
>> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
>>
>> Source code and binaries:
>>
>>
>> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.0-incubating-rc1/
>>
>> The vote will be open for at least 72 hours.
>>
>> The vote will be open for 72 hours.
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 do not release this package because...
>>
>> Thank you,
>> Jia Yu
>>
>>
>>

Re: [VOTE] Release Apache AGE (incubating) version 0.3.0 (RC1)

[Felix Cheung]

+1

Notes from checks:
incubating in name
the file should probably be called
  apache-age-0.3.0.rc0-incubating.tar.gz
  instead of incubator-age-0.3.0.rc0-incubating.tar.gz
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers



From: Eya Badal 
Sent: Tuesday, February 2, 2021 3:11:10 PM
To: dev@age.apache.org 
Subject: [VOTE] Release Apache AGE (incubating) version 0.3.0 (RC1)

Please vote on releasing the following candidate as Apache AGE version 0.3.0

The vote is open now and until February 5th at 3:11 PM PST and passes if a 
majority +1 votes are cast, with a minimum of 3 +1 votes.

[ ] +1 Release this package as Apache AGE 0.3.0
[ ] -1 Do not release this package because ...


To learn more about Apache AGE, please see http://age.apache.org/

Please note that this is the first Apache release for Apache AGE.


The tag to be voted on is v0.3.0.rc0-incubating (commit 
549ac9ff63337f64a9c19d8b9950b89ae412edee):
https://github.com/apache/incubator-age/tree/v0.3.0.rc0-incubating

The release files, including signatures, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/age/

Signatures used for AGE RCs can be found in this file:
https://dist.apache.org/repos/dist/dev/incubator/age/KEYS

The fingerprint of key to sign release artifacts:
FD8B 268F 784A CE10 F201  E63B C063 8775 6375 38D2

The notes corresponding to this release can be found at:
https://github.com/apache/incubator-age/releases/tag/v0.3.0.rc0-incubating


Thank you very much,
Eya Badal

Re: [VOTE] Release Apache Sedona 1.0.0-incubating rc1

[Felix Cheung]

Please - any one more vote for this?

On Wed, Feb 3, 2021 at 8:36 PM Ming Wen  wrote:

> +1 (binding)
>
> I checked:
> - Incubating in name
> - Checksums and PGP signatures are valid
> - DISCLAIMER-WIP exists
> - LICENSE and NOTICE look OK
>
> Thanks,
> Ming Wen, Apache APISIX PMC Chair
> Twitter: _WenMing
>
>
> Jia Yu  于2021年2月4日周四 上午11:47写道：
>
> > Dear all,
> >
> > We need to collect more votes in order to get this approved. Please take
> a
> > look at our release when you have time.
> >
> > Thank you very much!
> > Jia
> >
> > On Fri, Jan 29, 2021 at 1:00 PM Felix Cheung 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Carry from dev@
> > >
> > >
> > > On Thu, Jan 28, 2021 at 10:02 PM Jia Yu  wrote:
> > >
> > >> Dear all,
> > >>
> > >> I would like to start a vote for the first release of Apache Sedona
> > >> 1.0.0-incubating rc1
> > >>
> > >> Sedona community vote thread:
> > >>
> > >>
> >
> https://lists.apache.org/thread.html/r1c9406f0ba7b1eb942c03744ebe406344e1cc0bba8ae96430c66f63c%40%3Cdev.sedona.apache.org%3E
> > >>
> > >> Sedona community vote result thread:
> > >>
> > >>
> >
> https://lists.apache.org/thread.html/r462bd458b6542ad1bf8994e11717d8924365bfc3bb6282dc6acd5709%40%3Cdev.sedona.apache.org%3E
> > >>
> > >> Release note:
> > >>
> > >>
> >
> https://sedona.staged.apache.org/download/GeoSpark-All-Modules-Release-notes/#sedona-100
> > >>
> > >> Build instructions:
> > >> https://sedona.staged.apache.org/download/compile/
> > >>
> > >> GitHub tag:
> > >>
> > >>
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.0-incubating-rc1
> > >>
> > >> GPG public key to verify the Release:
> > >> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
> > >>
> > >> Source code and binaries:
> > >>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.0-incubating-rc1/
> > >>
> > >> The vote will be open for at least 72 hours.
> > >>
> > >> The vote will be open for 72 hours.
> > >> [ ] +1 approve
> > >> [ ] +0 no opinion
> > >> [ ] -1 do not release this package because...
> > >>
> > >> Thank you,
> > >> Jia Yu
> > >>
> > >
> >
>

Re: Stream-stream join in structured streaming

[Felix Cheung]

This could be highly interesting!


From: Youngwoo Kim (김영우) 
Sent: Monday, February 1, 2021 7:03:36 PM
To: Jia Yu 
Cc: dev@sedona.apache.org 
Subject: Re: Stream-stream join in structured streaming

Got it, thank you Jia for noticing that!

Youngwoo

On Tue, Feb 2, 2021 at 11:56 AM Jia Yu  wrote:

> Hi Youngwoo,
>
> We are aware that the current SQL spatial join does not support streaming
> tables. The Sedona support of Spark structured streaming is on our roadmap
> but it won't be available soon.
>
> Thanks,
> Jia
>
> On Sun, Jan 31, 2021 at 9:31 PM Youngwoo Kim (김영우) 
> wrote:
>
>> Hi,
>>
>> I'm looking into spatial range query using Apache Sedona in spark
>> structured streaming. In my test code, I joined two streams using
>> `st_contains` like following:
>>
>> Dataset fenced = spark.sql(
>> >   "SELECT * FROM poly, pts WHERE
>> > ST_Contains(ST_PolygonFromText(poly.value,','),
>> > ST_PointFromText(pts.value,','))");
>>
>>
>> I created two streams from `sparkSession.readStream()` and created two
>> views 'poly' and 'pts' respectively. As you expect, I wanted to know
>> whether the polygon contains the point.
>>
>> However, It does not work and I get an exception like this:
>>
>> Caused by: org.apache.spark.sql.AnalysisException: Stream-stream join
>> > without equality predicate is not supported;;
>> >   Join Inner,
>> >  **org.apache.spark.sql.geosparksql.expressions.ST_Contains$**
>>
>>
>> Looks like structured streaming has a restriction on that kind of join
>> query.
>>
>> Please let me know if there is a workaround for spatial joins and also,
>> any
>> plans to support joins in  structured streaming from Sedona.
>>
>> Spark 3.0.1 and GeoSpark 1.3.2-SNAPSHOT for my test env.
>>
>> Thanks,
>> Youngwoo
>>
>

Re: Podling Pinot Report Reminder - February 2021

[Felix Cheung]

Reminder



From: jmcl...@apache.org 
Sent: Wednesday, January 20, 2021 10:20:06 PM
To: d...@pinot.incubator.apache.org 
Subject: Podling Pinot Report Reminder - February 2021

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, 17 February 2021.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, February 03).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/February2021

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Re: Podling Sedona Report Reminder - February 2021

[Felix Cheung]

Reminder



From: jmcl...@apache.org 
Sent: Wednesday, January 20, 2021 10:20:08 PM
To: d...@sedona.incubator.apache.org 
Subject: Podling Sedona Report Reminder - February 2021

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, 17 February 2021.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, February 03).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/February2021

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: [VOTE] Release Apache Sedona 1.0.0-incubating rc1

[Felix Cheung]

+1 (binding)

Carry from dev@


On Thu, Jan 28, 2021 at 10:02 PM Jia Yu  wrote:

> Dear all,
>
> I would like to start a vote for the first release of Apache Sedona
> 1.0.0-incubating rc1
>
> Sedona community vote thread:
>
> https://lists.apache.org/thread.html/r1c9406f0ba7b1eb942c03744ebe406344e1cc0bba8ae96430c66f63c%40%3Cdev.sedona.apache.org%3E
>
> Sedona community vote result thread:
>
> https://lists.apache.org/thread.html/r462bd458b6542ad1bf8994e11717d8924365bfc3bb6282dc6acd5709%40%3Cdev.sedona.apache.org%3E
>
> Release note:
>
> https://sedona.staged.apache.org/download/GeoSpark-All-Modules-Release-notes/#sedona-100
>
> Build instructions:
> https://sedona.staged.apache.org/download/compile/
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.0-incubating-rc1
>
> GPG public key to verify the Release:
> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.0-incubating-rc1/
>
> The vote will be open for at least 72 hours.
>
> The vote will be open for 72 hours.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
>
> Thank you,
> Jia Yu
>

Re: [VOTE] Apache Sedona (incubating) rc1

[Felix Cheung]

Let’s close this vote and move to IPMC

On Wed, Jan 27, 2021 at 8:30 AM Mo Sarwat  wrote:

> I vote +1
>
> On Wed, Jan 20, 2021 at 1:26 AM Jia Yu  wrote:
>
> > Hi all,
> >
> > This is a call for vote on Apache Sedona (incubating) 1.0.0 rc1. Please
> > refer to the changes listed at the bottom of this email.
> >
> > Release note:
> >
> >
> https://sedona.staged.apache.org/download/GeoSpark-All-Modules-Release-notes/#sedona-100
> >
> > Build instructions:
> > https://sedona.staged.apache.org/download/compile/
> >
> > GitHub tag:
> >
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.0-incubating-rc1
> >
> > GPG public key to verify the Release:
> > https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
> >
> > Source code and binaries:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.0-incubating-rc1/
> >
> > The vote will be open for at least 72 hours or until a majority of at
> least
> > 3 +1 PMC votes are cast
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove with the reason
> >
> > Checklist for reference (because of DISCLAIMER-WIP, other checklist items
> > are not blockers):
> >
> > [ ] Download links are valid.
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> > [ ] DISCLAIMER is included.
> >
> > [ ] Source code artifacts have correct names matching the current
> release.
> >
> > For a detailed checklist  please refer to:
> >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Changes from the last failed vote (let's call it rc0 :-) ):
> > 1. Version changed from "1.0.0-incubator" to "1.0.0-incubating"
> > 2. Source code and binary now hosted on dist/dev/incubator/sedona/
> > 3. Source code and binary now are signed by RSA-4096 key with
> > ji...@apache.org
> > 4. Source code and binary now use sha512 checksum
> > 5. Binaries are not staged on repository.apache.org yet. I will stage
> them
> > after the vote passes.
> > 6. The compressed source code size changed from 600+ MB to 100+ MB, by
> > remove duplicate test data. Will find a way to further in the future
> > releases.
> > 7. GeoTools (LGPL license, ASF Category X license) binaries have been
> > completed removed from Sedona binaries. Users have to compile the source
> > code by themselves if they want to use ShapefileReader and CRS
> > Transformation.
> >
> > @fengji...@gmail.com  Von, the GitHub tag is called
> > "sedona-1.0.0-incubating-rc1" which has "sedona" prefix. This is because
> > our GitHub tags include old tags for GeoSpark. To differentiate Sedona
> tags
> > from old tags, I intend to add the "sedona" prefix.
> >
> > Thank you very much!
> > Jia
> >
>

Re: [DISCUSS] Zeppelin community sync up meeting

[Felix Cheung]

+1


From: Eric Pugh 
Sent: Tuesday, January 26, 2021 5:28:59 AM
To: users 
Subject: Re: [DISCUSS] Zeppelin community sync up meeting

I’d advocate for a regular quarterly run well versus a monthly that ends up 
sparsely attended and a scramble to setup.   The general idea is fantastic.

On Jan 25, 2021, at 10:37 PM, moon soo Lee 
mailto:m...@apache.org>> wrote:

+1  

Looking forward to it!

On Mon, Jan 25, 2021 at 6:20 PM Jeff Zhang 
mailto:zjf...@gmail.com>> wrote:
Hi Bill,

That's right, it has been more than one year we haven't do community sync up. 
I'd like to continue that to bring the community together for more wide 
discussion around zeppelin.

Bill Brooks mailto:wwbro...@gmail.com>> 于2021年1月26日周二 
上午10:11写道：
This is a great idea, but I thought that Mei Long was already putting
these events together and prior to the pandemic, they were happening.

Bill

On Mon, Jan 25, 2021 at 3:09 PM Jeff Zhang 
mailto:zjf...@gmail.com>> wrote:
>
> Hi folks (users & developers),
>
> I'd like to raise this discussion about regular community sync up meeting to 
> discuss various things of Zeppelin. You may know me that I have been active 
> in the Zeppelin community for the last 4 years. I believe Zeppelin is a very 
> promising and important project in the data science and big data area. But it 
> needs more community involvement to improve it ,no matter whether you are 
> zeppelin users or zeppelin developers. I hope this kind of sync up meeting 
> can gather people who are interested in zeppelin together, and let's discuss 
> what we can do to make zeppelin standout in the data science and big data 
> area.
>
> I hope it will be a regular sync up meeting, maybe one time per month. Let us 
> know whether you are interested in such kind of regular sync up meeting and 
> what kind of things do you like to discuss.
>
> --
> Best Regards
>
> Jeff Zhang


--
Best Regards

Jeff Zhang

___
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com | 
My Free/Busy
Co-Author: Apache Solr Enterprise Search Server, 3rd 
Ed
This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.

Re: [VOTE] Apache Sedona (incubating) rc1

[Felix Cheung]

+1

I checked the updated package, unpacked it etc.
Since I’ve already checked the source at git tag. I sign off on this -
thank you!


On Mon, Jan 25, 2021 at 12:21 AM Jia Yu  wrote:

> Hi Felix,
>
> Thank you very much for your comments.
>
> For your comments,
>
> 1. Fixed. The rebuilt and signed tarballs are on
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.0-incubating-rc1/
> 2. Fixed. I use "apache-sedona-1.0.0-incubating-src"
> and "apache-sedona-1.0.0-incubating-bin". "1.0.0" is before "incubating",
> this is to make it consistent with the version number in POM.
>
> For the staging repo, I just staged all artifacts on repository.apache.org
> .
>
> For the typos and broken links in compile doc, I have fixed them and moved
> this to "Publish code": https://sedona.staged.apache.org/download/publish/.
> The "compile code" is still available:
> https://sedona.staged.apache.org/download/compile/
>
> Regards,
> Jia
>
> On Sat, Jan 23, 2021 at 5:46 PM Felix Cheung 
> wrote:
>
>> 1/ the tarball should unpack to incubator-sedona-sedona-1.0.0-incubating
>> and not incubator-sedona-sedona-1.0.0-incubating-rc1 - this is because
>> once
>> the vote is passed, you will not be rebuilding the tarball - as the one we
>> voted on, signed etc, that one will be the actual release.
>>
>> 2. also typically the name of the unpacked directory should
>> be apache-sedona-incubating-1.0.0-src (the tarball should be
>> named apache-sedona-incubating-1.0.0-src.tar.gz)
>>
>> So let's rebuild the tarball, resign - we don't have to change the git tag
>> (so the source doesn't have to be reviewed again)
>>
>> additional notes:
>>
>> You can actually stage artifacts on repository.apache.org without having
>> it
>> published - in the staging repo
>> https://repository.apache.org/content/groups/staging/org/apache/
>>
>> These links on the compile page for the website seems wrong (
>> https://sedona.staged.apache.org/sedona.apache.org)
>> also there is a typo "will"
>>
>>1. Use the copied content to replace all content in asf-site branch and
>>upload to GitHub. Then sedona.apache.org
>><https://sedona.staged.apache.org/sedona.apache.org> wil be
>>automatically updated.
>>2. You can also push the content to asf-staging branch. The staging
>>website will be then updated: sedona.staged.apache.org
>><https://sedona.staged.apache.org/sedona.staged.apache.org>
>
>
>>
>> Checklist verified:
>> - incubating in name
>> - signature and hash fine
>> - DISCLAIMER is fine
>> - LICENSE and NOTICE are fine
>> - No unexpected binary files
>> - All source files have ASF headers
>> - compile from source
>>
>>
>> On Wed, Jan 20, 2021 at 12:26 AM Jia Yu  wrote:
>>
>> > Hi all,
>> >
>> > This is a call for vote on Apache Sedona (incubating) 1.0.0 rc1. Please
>> > refer to the changes listed at the bottom of this email.
>> >
>> > Release note:
>> >
>> >
>> https://sedona.staged.apache.org/download/GeoSpark-All-Modules-Release-notes/#sedona-100
>> >
>> > Build instructions:
>> > https://sedona.staged.apache.org/download/compile/
>> >
>> > GitHub tag:
>> >
>> >
>> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.0-incubating-rc1
>> >
>> > GPG public key to verify the Release:
>> > https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
>> >
>> > Source code and binaries:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.0-incubating-rc1/
>> >
>> > The vote will be open for at least 72 hours or until a majority of at
>> least
>> > 3 +1 PMC votes are cast
>> >
>> > Please vote accordingly:
>> >
>> > [ ] +1 approve
>> >
>> > [ ] +0 no opinion
>> >
>> > [ ] -1 disapprove with the reason
>> >
>> > Checklist for reference (because of DISCLAIMER-WIP, other checklist
>> items
>> > are not blockers):
>> >
>> > [ ] Download links are valid.
>> >
>> > [ ] Checksums and PGP signatures are valid.
>> >
>> > [ ] DISCLAIMER is included.
>> >
>> > [ ] Source code artifacts have correct names matching the current
>> release.
>> >
>> > For a detailed checklist  please refer to:
>> >
>> >
>> https

Re: [VOTE] Apache Sedona (incubating) rc1

[Felix Cheung]

1/ the tarball should unpack to incubator-sedona-sedona-1.0.0-incubating
and not incubator-sedona-sedona-1.0.0-incubating-rc1 - this is because once
the vote is passed, you will not be rebuilding the tarball - as the one we
voted on, signed etc, that one will be the actual release.

2. also typically the name of the unpacked directory should
be apache-sedona-incubating-1.0.0-src (the tarball should be
named apache-sedona-incubating-1.0.0-src.tar.gz)

So let's rebuild the tarball, resign - we don't have to change the git tag
(so the source doesn't have to be reviewed again)

additional notes:

You can actually stage artifacts on repository.apache.org without having it
published - in the staging repo
https://repository.apache.org/content/groups/staging/org/apache/

These links on the compile page for the website seems wrong (
https://sedona.staged.apache.org/sedona.apache.org)
also there is a typo "will"

   1. Use the copied content to replace all content in asf-site branch and
   upload to GitHub. Then sedona.apache.org
    wil be
   automatically updated.
   2. You can also push the content to asf-staging branch. The staging
   website will be then updated: sedona.staged.apache.org
   

Checklist verified:
- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers
- compile from source


On Wed, Jan 20, 2021 at 12:26 AM Jia Yu  wrote:

> Hi all,
>
> This is a call for vote on Apache Sedona (incubating) 1.0.0 rc1. Please
> refer to the changes listed at the bottom of this email.
>
> Release note:
>
> https://sedona.staged.apache.org/download/GeoSpark-All-Modules-Release-notes/#sedona-100
>
> Build instructions:
> https://sedona.staged.apache.org/download/compile/
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.0-incubating-rc1
>
> GPG public key to verify the Release:
> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.0-incubating-rc1/
>
> The vote will be open for at least 72 hours or until a majority of at least
> 3 +1 PMC votes are cast
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference (because of DISCLAIMER-WIP, other checklist items
> are not blockers):
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist  please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Changes from the last failed vote (let's call it rc0 :-) ):
> 1. Version changed from "1.0.0-incubator" to "1.0.0-incubating"
> 2. Source code and binary now hosted on dist/dev/incubator/sedona/
> 3. Source code and binary now are signed by RSA-4096 key with
> ji...@apache.org
> 4. Source code and binary now use sha512 checksum
> 5. Binaries are not staged on repository.apache.org yet. I will stage them
> after the vote passes.
> 6. The compressed source code size changed from 600+ MB to 100+ MB, by
> remove duplicate test data. Will find a way to further in the future
> releases.
> 7. GeoTools (LGPL license, ASF Category X license) binaries have been
> completed removed from Sedona binaries. Users have to compile the source
> code by themselves if they want to use ShapefileReader and CRS
> Transformation.
>
> @fengji...@gmail.com  Von, the GitHub tag is called
> "sedona-1.0.0-incubating-rc1" which has "sedona" prefix. This is because
> our GitHub tags include old tags for GeoSpark. To differentiate Sedona tags
> from old tags, I intend to add the "sedona" prefix.
>
> Thank you very much!
> Jia
>

Re: Request for First AGE Apache Release Review - VOTE

[Felix Cheung]

Thanks for the updates.

For disclaimer: it is your first release, so it is likely something is off (for 
example, you have a dependency that is not compatible with Apache license and 
normally will not be possible to release with) it is just easier to get through 
the process. The community can decide if you want to go this route or not.

For OpenCypher - if it is a public spec from OpenCypher, it will be best not to 
include a file but link to it. Even if license compatible it is best not to 
include files, source code etc from another project because then proper 
attribution should be there (typically in the LICENSE or NOTICE file)

See bundled dependencies here https://infra.apache.org/licensing-howto.html



From: Eya Badal 
Sent: Monday, January 18, 2021 7:32 AM
To: dev@age.apache.org
Subject: Re: Request for First AGE Apache Release Review - VOTE

Hi Felix,

I just want to mention some points.

1-I did update the svn with new files. The unzipping to different names is 
fixed now.
2-I also removed the md5 file and KEYS file from the svn and source 
distribution.
3-As I mentioned before the OpenCypher is based on Apache License and it is 
included.
4-Regarding the DISCLAIMER-WIP:
We do not have any tasks to do or tasks pending and not sure if we have to go 
by DISCLAIMER-WIP. What is your advice?

All the licenses are there and I do not have anything for pending tasks so I am 
not sure if we should use Standard or Work in Progress disclaimer. Please 
advise.

We will wait for your advice and then call for a VOTE.

Best regards,

On 2021/01/18 02:59:15, Felix Cheung  wrote:
> Yes. See the link I included in my reply for subject, format and content.
>
>
> 
> From: Eya Badal 
> Sent: Sunday, January 17, 2021 6:30:04 PM
> To: dev@age.apache.org 
> Subject: Re: Request for First AGE Apache Release Review - VOTE
>
> Thank you very much, Flex. I appreciate the feedback.
> >Where should I post the thread vote? Should I post it in AGE Dev list and 
> >ask everyone to vote?
>
>
> On 2021/01/15 02:20:01, Felix Cheung  wrote:
> > Did you have a vote thread? Anyone and everyone can vote, it shouldn’t be 
> > just the mentor.
> >
> > A good vote thread might be like:
> > http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Release-Spark-3-1-0-RC1-td30524.html
> >
> > 1. md5 - should not include
> >I will remove this file.
> >
> > 2. apache-age-0.3.0-incubating-src.tar.gz unpack into a 
> > apache-age-0.3.0-incubating-src.zip
> >  and that unpack into __MACOSX/apache-age-0.3.0-incubating-src/
> > This is very strange. please check the tar.gz file.
> >
> >I am not sure why this happened but I will take care of it and make sure it 
> >is consistent.
> >
> > 3.
> > I'd suggest use DISCLAIMER-WIP
> > https://incubator.apache.org/guides/releasemanagement.html#choice_of_disclaimers
> >Any specific reason why not using Standard Disclaimer?
> >
> > 4.
> > openCypher/openCypher9.pdf
> > maybe don't include this in the source? where is the file from? is there a 
> > possible licensing issue?
> >
> >It won't be any licensing issue since OpenCypher is based on Apache License 
> >as well which is included in the licensing file.
> > 5,
> > KEYS.txt
> > don't include inside the source distribution - this should not be in git 
> > repo
> > I will remove this as well.
> >
> >Thank you again and please advise if you have any other suggestions or 
> >thoughts.
> > 
> >
> > From: Eya Badal 
> > Sent: Wednesday, January 13, 2021 12:00:26 PM
> > To: dev@age.apache.org 
> > Subject: Request for First AGE Apache Release Review - VOTE
> >
> > Dear Mentors,
> >
> > We prepared the first Apache release and it is available now on the 
> > following link:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/age/
> >
> > Could you please review and approve.
> >
> > Best regards,
> > Eya
> >
>

Re: Request for First AGE Apache Release Review - VOTE

[Felix Cheung]

Yes. See the link I included in my reply for subject, format and content.



From: Eya Badal 
Sent: Sunday, January 17, 2021 6:30:04 PM
To: dev@age.apache.org 
Subject: Re: Request for First AGE Apache Release Review - VOTE

Thank you very much, Flex. I appreciate the feedback.
>Where should I post the thread vote? Should I post it in AGE Dev list and ask 
>everyone to vote?


On 2021/01/15 02:20:01, Felix Cheung  wrote:
> Did you have a vote thread? Anyone and everyone can vote, it shouldn’t be 
> just the mentor.
>
> A good vote thread might be like:
> http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Release-Spark-3-1-0-RC1-td30524.html
>
> 1. md5 - should not include
>I will remove this file.
>
> 2. apache-age-0.3.0-incubating-src.tar.gz unpack into a 
> apache-age-0.3.0-incubating-src.zip
>  and that unpack into __MACOSX/apache-age-0.3.0-incubating-src/
> This is very strange. please check the tar.gz file.
>
>I am not sure why this happened but I will take care of it and make sure it is 
>consistent.
>
> 3.
> I'd suggest use DISCLAIMER-WIP
> https://incubator.apache.org/guides/releasemanagement.html#choice_of_disclaimers
>Any specific reason why not using Standard Disclaimer?
>
> 4.
> openCypher/openCypher9.pdf
> maybe don't include this in the source? where is the file from? is there a 
> possible licensing issue?
>
>It won't be any licensing issue since OpenCypher is based on Apache License as 
>well which is included in the licensing file.
> 5,
> KEYS.txt
> don't include inside the source distribution - this should not be in git repo
> I will remove this as well.
>
>Thank you again and please advise if you have any other suggestions or 
>thoughts.
> 
>
> From: Eya Badal 
> Sent: Wednesday, January 13, 2021 12:00:26 PM
> To: dev@age.apache.org 
> Subject: Request for First AGE Apache Release Review - VOTE
>
> Dear Mentors,
>
> We prepared the first Apache release and it is available now on the following 
> link:
>
> https://dist.apache.org/repos/dist/dev/incubator/age/
>
> Could you please review and approve.
>
> Best regards,
> Eya
>

Re: Request for First AGE Apache Release Review - VOTE

[Felix Cheung]

Did you have a vote thread? Anyone and everyone can vote, it shouldn’t be just 
the mentor.

A good vote thread might be like:
http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Release-Spark-3-1-0-RC1-td30524.html

1. md5 - should not include

2. apache-age-0.3.0-incubating-src.tar.gz unpack into a 
apache-age-0.3.0-incubating-src.zip
 and that unpack into __MACOSX/apache-age-0.3.0-incubating-src/
This is very strange. please check the tar.gz file.

3.
I'd suggest use DISCLAIMER-WIP
https://incubator.apache.org/guides/releasemanagement.html#choice_of_disclaimers

4.
openCypher/openCypher9.pdf
maybe don't include this in source? where is the file from? is there a possible 
licensing issue?

5,
KEYS.txt
don't include inside the source distribution - this should not be in git repo



From: Eya Badal 
Sent: Wednesday, January 13, 2021 12:00:26 PM
To: dev@age.apache.org 
Subject: Request for First AGE Apache Release Review - VOTE

Dear Mentors,

We prepared the first Apache release and it is available now on the following 
link:

https://dist.apache.org/repos/dist/dev/incubator/age/

Could you please review and approve.

Best regards,
Eya

Re: [VOTE] Release Apache Sedona (incubating) 1.0.0

[Felix Cheung]

To clarify, what on

Maven staging repository (search for "sedona", 12 artifacts in total):
https://repository.apache.org/#stagingRepositories

Is not source distribution. It’s the Maven Java repository of artifacts
(binaries)

Again the office ASF vote is on src.


On Wed, Jan 13, 2021 at 12:12 AM vongosling  wrote:

> Hi,
>
> I also checked the source code, the name of the decompressed file is
> incubator-sedona-sedona-1.0.0-incubator... It's confusing.
>
> And I see that the size of files reaches almost 600 MB +. There are a lot
> of HDF files. I just wonder do we have a plan to optimize here :-)
>
> Here's a list of the Apache Incubation Project releases[1] memo, which
> could solve some of my words. Remember, this is just a reference. For the
> initial release in apache, I generally recommend that we could solve some
> of the key issues at the beginning.
>
> [1] https://issues.apache.org/jira/browse/LEGAL-469
>
> vongosling  于2021年1月13日周三 下午3:43写道：
>
> >
> > I would like to make some more comments since the broken message as Felix
> > said.
> >
> > 4. It is recommended that the final package name be
> > sedona-core_2.11-incubating instead of [2](the source code is too large).
> > You must have at least src distribution(That's ok now, but do we only
> > distribute source code?). Use the sha512 signature.
> >
> > 5. I have not checked the copyright-related issues and the compilation is
> > not passed. I hope that the compilation can pass in rc2. At the same
> time,
> > I also call on our committer to help verify it carefully and carefully.
> We
> > are more strict in the first release. If careful enough, I'm sure we'll
> be
> > able to publish it before rc3.
> >
> > If you have any questions, refer to the voting results of other items in
> > the incubation list. Of course, you are welcome to discuss it in your
> email.
> >
> > [1] https://dist.apache.org/repos/dist/dev/incubator/
> > [1] https://repository.apache.org/#nexus-search;quick-sedona
> >
> > Felix Cheung  于2021年1月13日周三 下午1:59写道：
> >
> >> We should definitely have the source release on
> >> https://dist.apache.org/repos/dist/dev/incubator/
> >>
> >> We are voting for source release (and the git tag) - binaries are for
> >> convenience.
> >>
> >> Von, can you clarify the final package name inline? I think you are
> >> looking
> >> at the artifact ID not a package name?
> >>
> >>
> >> On Tue, Jan 12, 2021 at 6:09 PM vongosling  wrote:
> >>
> >> > I'd love to vote +1, but after I've looked at this release, I'm
> sorry, I
> >> > have to vote  -1. This is just the early stage of release, and I think
> >> we
> >> > have the ability to smooth the release standardization process for
> >> apache.
> >> > Here, I'll point out some of the issues I've identified:
> >> >
> >> > 1. The recommended name of the GitHub tag is 1.0.0-rc1(rc2, rc3...).
> >> This
> >> > allows you to trace the number of times before a successful release.
> >> > 2. The source code tarball needs to be uploaded to the Apache dist
> >> > repository [1] instead of the Stage repository.
> >> > 3. You are advised to use the Apache email address instead of
> >> > ja...@asu.edu
> >> > for GPG signatures.
> >> > 4. It is recommended that the final package name be
> >> > sedona-core_2.11-incubing instead of [1]. You must have at least src
> >> > distribution. Use the sha512 signature.
> >>
> >>
> >> Can you clarify? The link below is broken, and I’m not sure which you
> are
> >> referencing.
> >>
> >>
> >>
> >> >
> >> > 5. I have not checked the copyright-related issues and the compilation
> >> is
> >> > not passed. I hope that the compilation can pass in rc2. At the same
> >> time,
> >> > I also call on our committer to help verify it carefully and
> carefully.
> >> We
> >> > are more strict in the first release. If careful enough, I'm sure
> we'll
> >> be
> >> > able to publish it before rc3.
> >> >
> >> > If you have any questions, refer to the voting results of other items
> in
> >> > the incubation list. Of course, you are welcome to discuss it in your
> >> > email.
> >> >
> >> > [1] https://dist.apache.org/repos/dist/dev/incubator/
> >> > [1] https://repository.apache.org/#nexus-search;quick-sedon

Re: [VOTE] Release Apache Sedona (incubating) 1.0.0

[Felix Cheung]

We should definitely have the source release on
https://dist.apache.org/repos/dist/dev/incubator/

We are voting for source release (and the git tag) - binaries are for
convenience.

Von, can you clarify the final package name inline? I think you are looking
at the artifact ID not a package name?


On Tue, Jan 12, 2021 at 6:09 PM vongosling  wrote:

> I'd love to vote +1, but after I've looked at this release, I'm sorry, I
> have to vote  -1. This is just the early stage of release, and I think we
> have the ability to smooth the release standardization process for apache.
> Here, I'll point out some of the issues I've identified:
>
> 1. The recommended name of the GitHub tag is 1.0.0-rc1(rc2, rc3...). This
> allows you to trace the number of times before a successful release.
> 2. The source code tarball needs to be uploaded to the Apache dist
> repository [1] instead of the Stage repository.
> 3. You are advised to use the Apache email address instead of
> ja...@asu.edu
> for GPG signatures.
> 4. It is recommended that the final package name be
> sedona-core_2.11-incubing instead of [1]. You must have at least src
> distribution. Use the sha512 signature.


Can you clarify? The link below is broken, and I’m not sure which you are
referencing.



>
> 5. I have not checked the copyright-related issues and the compilation is
> not passed. I hope that the compilation can pass in rc2. At the same time,
> I also call on our committer to help verify it carefully and carefully. We
> are more strict in the first release. If careful enough, I'm sure we'll be
> able to publish it before rc3.
>
> If you have any questions, refer to the voting results of other items in
> the incubation list. Of course, you are welcome to discuss it in your
> email.
>
> [1] https://dist.apache.org/repos/dist/dev/incubator/
> [1] https://repository.apache.org/#nexus-search;quick-sedona
>
> Netanel Malka  于2021年1月12日周二 下午2:13写道：
>
> > Great Job!!
> > +1
> >
> > Netanel Malka
> >
> > On 2021/01/07 10:16:11, Jia Yu  wrote:
> > > Hi All,
> > >
> > > After a fruitful discussion about our first Apache Sedona release
> > > 1.0.0-incubator, the release has been created. This is a call for vote
> to
> > > release Apache Sedona (incubating) 1.0.0.
> > >
> > > Note that: the current sha1 and checksum verification of Sedona will
> > > require us to manually download artifact jars, sha1, asc from
> > > repository.apache.org 12 times each. It is very annoying. Please let
> me
> > > know if you have any suggestions to speed up the process.
> > >
> > > Release note:
> > >
> >
> https://sedona.staged.apache.org/download/GeoSpark-All-Modules-Release-notes/#sedona-100
> > >
> > > Build instructions:
> > > https://sedona.staged.apache.org/download/compile/
> > >
> > > Git tag:
> > >
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.0-incubator
> > >
> > > Maven staging repository (search for "sedona", 12 artifacts in total):
> > > https://repository.apache.org/#stagingRepositories
> > >
> > > Release Commit ID:
> > >
> >
> https://github.com/apache/incubator-sedona/commit/29f897bbcaf65aa5b5b28ea4e93c6b7e783d83a6
> > >
> > > GPG public key to verify the Release:
> > >
> >
> https://gist.githubusercontent.com/jiayuasu/8b6cc263c538148490f7a090ee1dbeab/raw/09d3821e2794ddf22542f74c0db5195cf5c1ff49/gpg-public-key.gpg
> > >
> > > The vote will be open for at least 72 hours or until a majority of at
> > least
> > > 3 +1 PMC votes are cast
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove with the reason
> > >
> > > Checklist for reference (because of DISCLAIMER-WIP, other checklist
> items
> > > are not blockers):
> > >
> > > [ ] Download links are valid.
> > >
> > > [ ] Checksums and PGP signatures are valid.
> > >
> > > [ ] DISCLAIMER is included.
> > >
> > > [ ] Source code artifacts have correct names matching the current
> > release.
> > >
> > > For a detailed checklist  please refer to:
> > >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > To verify the checksum,
> > > 1. open https://repository.apache.org
> > > 2 (1) click each release jar (12 in total) to see its current SHA1
> (under
> > > Artifact tab) (2) download .jar.sha1 to see the content of the uploaded
> > > sha1. This two should match
> > >
> > > To verify the GPG key (12 in total),
> > > gpg --import the-key-file
> > > gpg --verify xxx.jar.asc xxx.jar
> > >
> > > You should see something like "gpg: Good signature from "Jia Yu
> (Arizona
> > > State University Data Systems Lab) "  gpg: WARNING:
> This
> > > key is not certified with a trusted signature!"
> > >
> > > Thanks,
> > > Jia
> > >
> >
>
>
> --
> Nothing is impossible
>

Re: Sedona 1.0 Maven release is staged

[Felix Cheung]

Release review.

Note: with DISCLAIMER-WIP, these are not blockers to release.

website:
1. the website can add more links as described in this section:
https://www.apache.org/foundation/marks/pmcs#navigation
2. might need to add trademark attributions
https://www.apache.org/foundation/marks/pmcs#attributions

project source:
1. For LICENSE, we should add RAT check
https://creadur.apache.org/rat/#What_Is_Rat
2. This file seems to have an irregular header:
/incubator-sedona/zeppelin/index.js
3. These code file should have Apache v2 header:
/python/build_wheel.sh
/spark-version-converter.py
/python-adapter/src/test/scala/org/apache/sedona/python/wrapper/PythonTestSpec.scala
/python-adapter/src/test/scala/org/apache/sedona/python/wrapper/GeometrySample.scala
4.
/docs/api/javadoc/core/org/apache/sedona/core/geometryObjects/GeoJSONWriterNew.html
/docs/api/javadoc/*
are these doc under /docs/api/javadoc auto generated? if that is the case,
we probably shouldn't have the HTML committed in the repo
5.
/trunk/import/*
what is this for?
6. should add a small section on how to build (or link to) the project in
README.md


On Wed, Dec 30, 2020 at 6:24 PM Felix Cheung  wrote:

> Yes
> https://incubator.apache.org/guides/distribution.html#pypi
>
> Reminder: This should not be posted until we have Sedona and IPMC vote.
>
>
> On Wed, Dec 30, 2020 at 3:30 PM Jia Yu  wrote:
>
>> Hi Pawel,
>>
>> The only Pypi guideline that I can find is Incubator distribution
>> guideline: https://incubator.apache.org/guides/distribution.html
>>
>> If you scroll down to the bottom, you will see the section.
>>
>> @Felix Cheung  Felix, does Pawel need to be
>> aware of anything else, besides the incubator PyPi guideline?
>>
>> Thank you very much!
>> Jia
>>
>> On Wed, Dec 30, 2020 at 3:26 PM Jia Yu  wrote:
>>
>> > Hi Netanel,
>> >
>> > I have created a few demo projects:
>> > https://sedona.staged.apache.org/tutorial/GeoSpark-Runnable-DEMO/
>> > The source code is here:
>> > https://github.com/apache/incubator-sedona/tree/master/examples
>> >
>> > Does it look good?
>> >
>> > Thanks,
>> > Jia
>> >
>> > On Wed, Dec 30, 2020 at 1:06 PM Netanel Malka 
>> wrote:
>> >
>> >> Hi Jia,
>> >> That's great news!
>> >>
>> >> Happy and healthy New Year to everyone.
>> >>
>> >> They look fine to me.
>> >> Do you think it will be worth to use them within a demo project? (to
>> >> eliminate dependency issues) I can test it if we need it.
>> >>
>> >> BR,
>> >>
>> >>
>> >> Netanel Malka,
>> >> Big Data Consultant
>> >> [image: Description: Description: Description: Description:
>> >> cid:image001.jpg@01C85203.36A2AF30]
>> >> --
>> >> *From:* Paweł Kociński 
>> >> *Sent:* Wednesday, December 30, 2020 22:09
>> >> *To:* Jia Yu
>> >> *Cc:* dev@sedona.apache.org; Jinxuan Wu; Mohamed Sarwat; Netanel
>> Malka;
>> >> Zongsi Zhang; Felix Cheung; Netanel Malka
>> >> *Subject:* Re: Sedona 1.0 Maven release is staged
>> >>
>> >> Hi Jia,
>> >> Merry Christmas and Happy New Year to everyone.
>> >> I can definitely do that but I am not sure about the steps which I
>> should
>> >> follow to upload package under Apache project. Also should we sync this
>> >> processes, I mean Maven and PyPI release ?
>> >>
>> >> Regards,
>> >> Pawel
>> >>
>> >> śr., 30 gru 2020 o 08:43 Jia Yu  napisał(a):
>> >>
>> >>> Dear all,
>> >>>
>> >>> Merry Christmas and Happy New Year!
>> >>>
>> >>> After months of hard work, we are finally close to the Sedona
>> >>> 1.0.0-incubator release. I have staged Sedona 1.0.0 official release
>> on
>> >>> Nexus. This is a thread for collecting final feedback rather than a
>> voting
>> >>> thread.
>> >>>
>> >>> 1. I would like to ask all of you to take a look at the staged Maven
>> >>> releases (12 Sedona modules in total). Please learn how to access
>> Nexus
>> >>> from [1][2]
>> >>>
>> >>> @Mohamed Sarwat  @Netanel Malka <
>> netanel...@gmail.com> Would
>> >>> you please take a look at the staged releases?
>> >>>
>> >>> @Felix Cheung   Felix, could you please take
>> a
>> >>> look at the release as well? Your opinion is very important. If you
>> think
>> >>> everything is good, then I will call for a vote.
>> >>>
>> >>> 2. Python release on PyPi
>> >>> @Paweł Kociński  Pawel, could you please
>> >>> publish Sedona 1.0.0-incubator-SNAPSHOT to PyPi? Then we will use
>> that to
>> >>> call for a vote.
>> >>>
>> >>> I know many of you may be on vacation so no need to rush.
>> >>>
>> >>> [1]
>> >>>
>> https://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
>> >>> [2] Sedona staged website: https://sedona.staged.apache.org/
>> >>>
>> >>
>>
>

Re: Sedona 1.0 Maven release is staged

[Felix Cheung]

Yes
https://incubator.apache.org/guides/distribution.html#pypi

Reminder: This should not be posted until we have Sedona and IPMC vote.


On Wed, Dec 30, 2020 at 3:30 PM Jia Yu  wrote:

> Hi Pawel,
>
> The only Pypi guideline that I can find is Incubator distribution
> guideline: https://incubator.apache.org/guides/distribution.html
>
> If you scroll down to the bottom, you will see the section.
>
> @Felix Cheung  Felix, does Pawel need to be
> aware of anything else, besides the incubator PyPi guideline?
>
> Thank you very much!
> Jia
>
> On Wed, Dec 30, 2020 at 3:26 PM Jia Yu  wrote:
>
> > Hi Netanel,
> >
> > I have created a few demo projects:
> > https://sedona.staged.apache.org/tutorial/GeoSpark-Runnable-DEMO/
> > The source code is here:
> > https://github.com/apache/incubator-sedona/tree/master/examples
> >
> > Does it look good?
> >
> > Thanks,
> > Jia
> >
> > On Wed, Dec 30, 2020 at 1:06 PM Netanel Malka 
> wrote:
> >
> >> Hi Jia,
> >> That's great news!
> >>
> >> Happy and healthy New Year to everyone.
> >>
> >> They look fine to me.
> >> Do you think it will be worth to use them within a demo project? (to
> >> eliminate dependency issues) I can test it if we need it.
> >>
> >> BR,
> >>
> >>
> >> Netanel Malka,
> >> Big Data Consultant
> >> [image: Description: Description: Description: Description:
> >> cid:image001.jpg@01C85203.36A2AF30]
> >> --
> >> *From:* Paweł Kociński 
> >> *Sent:* Wednesday, December 30, 2020 22:09
> >> *To:* Jia Yu
> >> *Cc:* dev@sedona.apache.org; Jinxuan Wu; Mohamed Sarwat; Netanel Malka;
> >> Zongsi Zhang; Felix Cheung; Netanel Malka
> >> *Subject:* Re: Sedona 1.0 Maven release is staged
> >>
> >> Hi Jia,
> >> Merry Christmas and Happy New Year to everyone.
> >> I can definitely do that but I am not sure about the steps which I
> should
> >> follow to upload package under Apache project. Also should we sync this
> >> processes, I mean Maven and PyPI release ?
> >>
> >> Regards,
> >> Pawel
> >>
> >> śr., 30 gru 2020 o 08:43 Jia Yu  napisał(a):
> >>
> >>> Dear all,
> >>>
> >>> Merry Christmas and Happy New Year!
> >>>
> >>> After months of hard work, we are finally close to the Sedona
> >>> 1.0.0-incubator release. I have staged Sedona 1.0.0 official release on
> >>> Nexus. This is a thread for collecting final feedback rather than a
> voting
> >>> thread.
> >>>
> >>> 1. I would like to ask all of you to take a look at the staged Maven
> >>> releases (12 Sedona modules in total). Please learn how to access Nexus
> >>> from [1][2]
> >>>
> >>> @Mohamed Sarwat  @Netanel Malka 
> Would
> >>> you please take a look at the staged releases?
> >>>
> >>> @Felix Cheung   Felix, could you please take a
> >>> look at the release as well? Your opinion is very important. If you
> think
> >>> everything is good, then I will call for a vote.
> >>>
> >>> 2. Python release on PyPi
> >>> @Paweł Kociński  Pawel, could you please
> >>> publish Sedona 1.0.0-incubator-SNAPSHOT to PyPi? Then we will use that
> to
> >>> call for a vote.
> >>>
> >>> I know many of you may be on vacation so no need to rush.
> >>>
> >>> [1]
> >>>
> https://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
> >>> [2] Sedona staged website: https://sedona.staged.apache.org/
> >>>
> >>
>

Re: Sedona 1.0 Maven release is staged

[Felix Cheung]

Is there a git tag to review? Generally we review release from source,
rather than binaries.

Is it 887c43a488c995e2f4a9d827c432c81612e28d0d
?


On Wed, Dec 30, 2020 at 1:06 PM Netanel Malka  wrote:

> Hi Jia,
> That's great news!
>
> Happy and healthy New Year to everyone.
>
> They look fine to me.
> Do you think it will be worth to use them within a demo project? (to
> eliminate dependency issues) I can test it if we need it.
>
> BR,
>
>
> Netanel Malka,
> Big Data Consultant
> [image: Description: Description: Description: Description:
> cid:image001.jpg@01C85203.36A2AF30]
> --
> *From:* Paweł Kociński 
> *Sent:* Wednesday, December 30, 2020 22:09
> *To:* Jia Yu
> *Cc:* dev@sedona.apache.org; Jinxuan Wu; Mohamed Sarwat; Netanel Malka;
> Zongsi Zhang; Felix Cheung; Netanel Malka
> *Subject:* Re: Sedona 1.0 Maven release is staged
>
> Hi Jia,
> Merry Christmas and Happy New Year to everyone.
> I can definitely do that but I am not sure about the steps which I should
> follow to upload package under Apache project. Also should we sync this
> processes, I mean Maven and PyPI release ?
>
> Regards,
> Pawel
>
> śr., 30 gru 2020 o 08:43 Jia Yu  napisał(a):
>
>> Dear all,
>>
>> Merry Christmas and Happy New Year!
>>
>> After months of hard work, we are finally close to the Sedona
>> 1.0.0-incubator release. I have staged Sedona 1.0.0 official release on
>> Nexus. This is a thread for collecting final feedback rather than a voting
>> thread.
>>
>> 1. I would like to ask all of you to take a look at the staged Maven
>> releases (12 Sedona modules in total). Please learn how to access Nexus
>> from [1][2]
>>
>> @Mohamed Sarwat  @Netanel Malka  Would
>> you please take a look at the staged releases?
>>
>> @Felix Cheung   Felix, could you please take a
>> look at the release as well? Your opinion is very important. If you think
>> everything is good, then I will call for a vote.
>>
>> 2. Python release on PyPi
>> @Paweł Kociński  Pawel, could you please
>> publish Sedona 1.0.0-incubator-SNAPSHOT to PyPi? Then we will use that to
>> call for a vote.
>>
>
>> I know many of you may be on vacation so no need to rush.
>>
>> [1]
>> https://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
>> [2] Sedona staged website: https://sedona.staged.apache.org/
>>
>

Re: Recovering SparkR on CRAN?

[Felix Cheung]

We could just submit the latest release with the fix again. I would not
recommend waiting, often time there are some external changes that are not
caught, and a fix will need to go through a release vote.

What is the latest release with your fix? 3.0.1? I can put it in but will
need to make sure we can get hold of Shivaram.


On Tue, Dec 29, 2020 at 11:05 PM Hyukjin Kwon  wrote:

> Let me try in this release - I will have to ask some questions to both of
> you. I will email you guys offline or private mailing list.
> If I happen to be stuck for a difficult reason, I think we can consider
> dropping it as Dongjoon initially pointed out.
>
> 2020년 12월 30일 (수) 오후 1:59, Felix Cheung 님이 작성:
>
>> Ah, I don’t recall actually - maybe it was just missed?
>>
>> The last message I had, was in June when it was broken by R 4.0.1, which
>> was fixed.
>>
>>
>> On Tue, Dec 29, 2020 at 7:21 PM Hyukjin Kwon  wrote:
>>
>>> BTW, I remember I fixed all standing issues at
>>> https://issues.apache.org/jira/browse/SPARK-31918 and
>>> https://issues.apache.org/jira/browse/SPARK-32073.
>>> I wonder why other releases were not uploaded yet. Do you guys know any
>>> context or if there is a standing issue on this, @Felix Cheung
>>>  or @Shivaram Venkataraman
>>> ?
>>>
>>> 2020년 12월 23일 (수) 오전 11:21, Mridul Muralidharan 님이 작성:
>>>
>>>>
>>>> I agree, is there something we can do to ensure CRAN publish goes
>>>> through consistently and predictably ?
>>>> If possible, it would be good to continue supporting it.
>>>>
>>>> Regards,
>>>> Mridul
>>>>
>>>> On Tue, Dec 22, 2020 at 7:48 PM Felix Cheung 
>>>> wrote:
>>>>
>>>>> Ok - it took many years to get it first published, so it was hard to
>>>>> get there.
>>>>>
>>>>>
>>>>> On Tue, Dec 22, 2020 at 5:45 PM Hyukjin Kwon 
>>>>> wrote:
>>>>>
>>>>>> Adding @Shivaram Venkataraman  and @Felix
>>>>>> Cheung  FYI
>>>>>>
>>>>>> 2020년 12월 23일 (수) 오전 9:22, Michael Heuer 님이 작성:
>>>>>>
>>>>>>> Anecdotally, as a project downstream of Spark, we've been prevented
>>>>>>> from pushing to CRAN because of this
>>>>>>>
>>>>>>> https://github.com/bigdatagenomics/adam/issues/1851
>>>>>>>
>>>>>>> We've given up and marked as WontFix.
>>>>>>>
>>>>>>>michael
>>>>>>>
>>>>>>>
>>>>>>> On Dec 22, 2020, at 5:14 PM, Dongjoon Hyun 
>>>>>>> wrote:
>>>>>>>
>>>>>>> Given the current circumstance, I'm thinking of dropping it
>>>>>>> officially from the community release scope.
>>>>>>>
>>>>>>> It's because
>>>>>>>
>>>>>>> - It turns out that our CRAN check is insufficient to guarantee the
>>>>>>> availability of SparkR on CRAN.
>>>>>>>   Apache Spark 3.1.0 may not not available on CRAN, too.
>>>>>>>
>>>>>>> - In daily CIs, CRAN check has been broken frequently due to both
>>>>>>> our side and CRAN side issues. Currently, branch-2.4 is broken.
>>>>>>>
>>>>>>> - It also has a side-effect to cause some delays on the official
>>>>>>> release announcement after RC passes because each release manager takes 
>>>>>>> a
>>>>>>> look at it if he/she can recover it at that release.
>>>>>>>
>>>>>>> If we are unable to support SparkR on CRAN in a sustainable way,
>>>>>>> what about dropping it official instead?
>>>>>>>
>>>>>>> Then, it will alleviate burdens on release managers and improves
>>>>>>> daily CIs' stability by removing the CRAN check.
>>>>>>>
>>>>>>> Bests,
>>>>>>> Dongjoon.
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Dec 21, 2020 at 7:09 AM Dongjoon Hyun <
>>>>>>> dongjoon.h...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi, All.
>>>>>>>>
>>>>>>>> The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
>>>>>>>>
>>>>>>>>
>>>>>>>> https://cran-archive.r-project.org/web/checks/2020/2020-07-10_check_results_SparkR.html
>>>>>>>>
>>>>>>>> The latest three Apache Spark distributions (2.4.7/3.0.0/3.0.1) are
>>>>>>>> not published to CRAN and the lack of SparkR on CRAN has been 
>>>>>>>> considered a
>>>>>>>> non-release blocker.
>>>>>>>>
>>>>>>>> I'm wondering if we are aiming to recover it in Apache Spark 3.1.0.
>>>>>>>>
>>>>>>>> Bests,
>>>>>>>> Dongjoon.
>>>>>>>>
>>>>>>>
>>>>>>>

Re: Recovering SparkR on CRAN?

[Felix Cheung]

Ah, I don’t recall actually - maybe it was just missed?

The last message I had, was in June when it was broken by R 4.0.1, which
was fixed.


On Tue, Dec 29, 2020 at 7:21 PM Hyukjin Kwon  wrote:

> BTW, I remember I fixed all standing issues at
> https://issues.apache.org/jira/browse/SPARK-31918 and
> https://issues.apache.org/jira/browse/SPARK-32073.
> I wonder why other releases were not uploaded yet. Do you guys know any
> context or if there is a standing issue on this, @Felix Cheung
>  or @Shivaram Venkataraman
> ?
>
> 2020년 12월 23일 (수) 오전 11:21, Mridul Muralidharan 님이 작성:
>
>>
>> I agree, is there something we can do to ensure CRAN publish goes through
>> consistently and predictably ?
>> If possible, it would be good to continue supporting it.
>>
>> Regards,
>> Mridul
>>
>> On Tue, Dec 22, 2020 at 7:48 PM Felix Cheung 
>> wrote:
>>
>>> Ok - it took many years to get it first published, so it was hard to get
>>> there.
>>>
>>>
>>> On Tue, Dec 22, 2020 at 5:45 PM Hyukjin Kwon 
>>> wrote:
>>>
>>>> Adding @Shivaram Venkataraman  and @Felix
>>>> Cheung  FYI
>>>>
>>>> 2020년 12월 23일 (수) 오전 9:22, Michael Heuer 님이 작성:
>>>>
>>>>> Anecdotally, as a project downstream of Spark, we've been prevented
>>>>> from pushing to CRAN because of this
>>>>>
>>>>> https://github.com/bigdatagenomics/adam/issues/1851
>>>>>
>>>>> We've given up and marked as WontFix.
>>>>>
>>>>>michael
>>>>>
>>>>>
>>>>> On Dec 22, 2020, at 5:14 PM, Dongjoon Hyun 
>>>>> wrote:
>>>>>
>>>>> Given the current circumstance, I'm thinking of dropping it officially
>>>>> from the community release scope.
>>>>>
>>>>> It's because
>>>>>
>>>>> - It turns out that our CRAN check is insufficient to guarantee the
>>>>> availability of SparkR on CRAN.
>>>>>   Apache Spark 3.1.0 may not not available on CRAN, too.
>>>>>
>>>>> - In daily CIs, CRAN check has been broken frequently due to both our
>>>>> side and CRAN side issues. Currently, branch-2.4 is broken.
>>>>>
>>>>> - It also has a side-effect to cause some delays on the official
>>>>> release announcement after RC passes because each release manager takes a
>>>>> look at it if he/she can recover it at that release.
>>>>>
>>>>> If we are unable to support SparkR on CRAN in a sustainable way, what
>>>>> about dropping it official instead?
>>>>>
>>>>> Then, it will alleviate burdens on release managers and improves daily
>>>>> CIs' stability by removing the CRAN check.
>>>>>
>>>>> Bests,
>>>>> Dongjoon.
>>>>>
>>>>>
>>>>> On Mon, Dec 21, 2020 at 7:09 AM Dongjoon Hyun 
>>>>> wrote:
>>>>>
>>>>>> Hi, All.
>>>>>>
>>>>>> The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
>>>>>>
>>>>>>
>>>>>> https://cran-archive.r-project.org/web/checks/2020/2020-07-10_check_results_SparkR.html
>>>>>>
>>>>>> The latest three Apache Spark distributions (2.4.7/3.0.0/3.0.1) are
>>>>>> not published to CRAN and the lack of SparkR on CRAN has been considered 
>>>>>> a
>>>>>> non-release blocker.
>>>>>>
>>>>>> I'm wondering if we are aiming to recover it in Apache Spark 3.1.0.
>>>>>>
>>>>>> Bests,
>>>>>> Dongjoon.
>>>>>>
>>>>>
>>>>>

Re: Recovering SparkR on CRAN?

[Felix Cheung]

Ok - it took many years to get it first published, so it was hard to get
there.


On Tue, Dec 22, 2020 at 5:45 PM Hyukjin Kwon  wrote:

> Adding @Shivaram Venkataraman  and @Felix
> Cheung  FYI
>
> 2020년 12월 23일 (수) 오전 9:22, Michael Heuer 님이 작성:
>
>> Anecdotally, as a project downstream of Spark, we've been prevented from
>> pushing to CRAN because of this
>>
>> https://github.com/bigdatagenomics/adam/issues/1851
>>
>> We've given up and marked as WontFix.
>>
>>michael
>>
>>
>> On Dec 22, 2020, at 5:14 PM, Dongjoon Hyun 
>> wrote:
>>
>> Given the current circumstance, I'm thinking of dropping it officially
>> from the community release scope.
>>
>> It's because
>>
>> - It turns out that our CRAN check is insufficient to guarantee the
>> availability of SparkR on CRAN.
>>   Apache Spark 3.1.0 may not not available on CRAN, too.
>>
>> - In daily CIs, CRAN check has been broken frequently due to both our
>> side and CRAN side issues. Currently, branch-2.4 is broken.
>>
>> - It also has a side-effect to cause some delays on the official release
>> announcement after RC passes because each release manager takes a look at
>> it if he/she can recover it at that release.
>>
>> If we are unable to support SparkR on CRAN in a sustainable way, what
>> about dropping it official instead?
>>
>> Then, it will alleviate burdens on release managers and improves daily
>> CIs' stability by removing the CRAN check.
>>
>> Bests,
>> Dongjoon.
>>
>>
>> On Mon, Dec 21, 2020 at 7:09 AM Dongjoon Hyun 
>> wrote:
>>
>>> Hi, All.
>>>
>>> The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
>>>
>>>
>>> https://cran-archive.r-project.org/web/checks/2020/2020-07-10_check_results_SparkR.html
>>>
>>> The latest three Apache Spark distributions (2.4.7/3.0.0/3.0.1) are not
>>> published to CRAN and the lack of SparkR on CRAN has been considered a
>>> non-release blocker.
>>>
>>> I'm wondering if we are aiming to recover it in Apache Spark 3.1.0.
>>>
>>> Bests,
>>> Dongjoon.
>>>
>>
>>

Re: JIRA notification

[Felix Cheung]

I’d think you just open a ticket on INFRA, similar to this

https://issues.apache.org/jira/browse/INFRA-20830


On Tue, Dec 8, 2020 at 2:21 AM Jia Yu  wrote:

> Hi Felix,
>
> I notice that JIRA does not send notifications to us or the dev list so I
> sometimes miss users' JIRA ticket.
>
> When I try to configure it here:
> https://issues.apache.org/jira/plugins/servlet/project-config/SEDONA/notifications
>
> It says I should contact the admin. Should I send an email to
> j...@apache.org?
>
> Thank you!
> Jia
>

Re: Podling Crail Report Reminder - December 2020

[Felix Cheung]

Reminder :


From: jmcl...@apache.org 
Sent: Saturday, November 28, 2020 4:01:28 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Crail Report Reminder - December 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, 16 December 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, December 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/December2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Age Report Reminder - December 2020

[Felix Cheung]

Reminder:



From: jmcl...@apache.org 
Sent: Saturday, November 28, 2020 4:01:34 PM
To: d...@age.incubator.apache.org 
Subject: Podling Age Report Reminder - December 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, 16 December 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, December 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/December2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: First Sedona release

[Felix Cheung]

Thx Jia.

Then it falls under optional use
https://www.apache.org/legal/resolved.html#optional

Which is totally fine.


On Mon, Nov 23, 2020 at 6:50 PM Jia Yu  wrote:

> Thank you, Felix. I will use the WIP disclaimer.
>
> To answer Jim's question, GeoTools components use different licenses:
> https://docs.geotools.org/latest/userguide/welcome/license.html
>
> GT-main uses BSD, so its binary can be included in Sedona's release.
> Other components in GeoTools use LGPL, but Sedona only uses them for CRS
> transformation. I already set the dependency scope to "provided" in
> Sedona's POM.xml. If a user wants to use CRS transformation in Sedona, they
> will have to add some GeoTools library by themselves.
>
>
> On Mon, Nov 23, 2020 at 6:24 PM Felix Cheung 
> wrote:
>
> > On Mon, Nov 23, 2020 at 6:03 PM Felix Cheung 
> > wrote:
> >
> > > I’d strongly recommend the community to move towards the first release
> > > with the WIP disclaimer
> > >
> > >
> >
> https://incubator.apache.org/policy/incubation.html#work_in_progress_disclaimer
> > >
> > > https://incubator.apache.org/policy/incubation.html#releases
> > >
> > >
> > > As for the LGPL dependency specifically, a replacement will be needed?
> > >
> >
> >
> > To clarify, ok to note in the WIP disclaimer- so it can be released with
> > this.
> >
> >
> >
> > >
> > > On 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.org/legal/resolved.html#category-x)
> > >>
> > >> 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
> > >>
> > >> 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 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 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. In order to
> make
> > it
> > >> >> happen,
> > >> >>
> > >> >> Finalize coding and documentation before Dec 6:
> > >> >> 1. I believe the Move-to-JTS PR will be done in around one week.
> > >> >> 2. Then we can accept Pawel' Python RDD-DF Adapter PR, if necessary
> > >> >> 3. I will work on Sedona documentation.
> > >> >> 4. @Netanel will work on Sedona support of Spark 2.4 and Scala
> 2.11.
> > I
> > >> will
> > >> >> first create a branch for it to illustrate some necessary changes
> in
> > >> Sedona
> > >> >> SQL for Spark 2.4.
> > >> >>
> > >> >> Final walk-through before Dec 13
> > >> >> 1. Netanel can test the release management for Sedona.
> > >> >> 2. Other committers can go through the docs, release notes
> > >> >>
> > >> >> Community voting before Dec 20
> > >> >> 1. Sedona community voting: before Dec 16
> > >> >> 2. Apache Incubator voting: before Dec 20
> > >> >>
> > >> >> Push to Maven Central and PyPi before Dec 24
> > >> >>
> > >> >> Please feel free to comment if you have any suggestions!
> > >> >>
> > >> >> Jia
&

Re: First Sedona release

[Felix Cheung]

On Mon, Nov 23, 2020 at 6:03 PM Felix Cheung  wrote:

> I’d strongly recommend the community to move towards the first release
> with the WIP disclaimer
>
> https://incubator.apache.org/policy/incubation.html#work_in_progress_disclaimer
>
> https://incubator.apache.org/policy/incubation.html#releases
>
>
> As for the LGPL dependency specifically, a replacement will be needed?
>


To clarify, ok to note in the WIP disclaimer- so it can be released with
this.



>
> On 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.org/legal/resolved.html#category-x)
>>
>> 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
>>
>> 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 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 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. In order to make it
>> >> happen,
>> >>
>> >> Finalize coding and documentation before Dec 6:
>> >> 1. I believe the Move-to-JTS PR will be done in around one week.
>> >> 2. Then we can accept Pawel' Python RDD-DF Adapter PR, if necessary
>> >> 3. I will work on Sedona documentation.
>> >> 4. @Netanel will work on Sedona support of Spark 2.4 and Scala 2.11. I
>> will
>> >> first create a branch for it to illustrate some necessary changes in
>> Sedona
>> >> SQL for Spark 2.4.
>> >>
>> >> Final walk-through before Dec 13
>> >> 1. Netanel can test the release management for Sedona.
>> >> 2. Other committers can go through the docs, release notes
>> >>
>> >> Community voting before Dec 20
>> >> 1. Sedona community voting: before Dec 16
>> >> 2. Apache Incubator voting: before Dec 20
>> >>
>> >> Push to Maven Central and PyPi before Dec 24
>> >>
>> >> Please feel free to comment if you have any suggestions!
>> >>
>> >> Jia
>> >>
>> >> On Sun, Nov 22, 2020 at 9:51 AM Paweł Kociński <
>> pawel93kocin...@gmail.com>
>> >> wrote:
>> >>
>> >>> Hi,
>> >>> I saw some users reported need to improve Python RDD API in two
>> >> scenarios:
>> >>> - converting spatial flat join result to df
>> >>> - saving spatial flat join result directly to external storage
>> >>>
>> >>> Currently SerDe between jvm and Python causes additional time needed
>> to
>> >>> compute the result. I have a local 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 08:29 Jia Yu  napisał(a):
>> >>>
>> >>>> Dear all,
>> >>>>
>> >>>> Thanks for all your suggestions.
>> >>>>
>> >>>> 1. To completely solve the long-overdue JTS issue, I made a Sedona PR
>> >> and
>> >>>> two JTS PRs. @Jim Hughes  , @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/a

Re: First Sedona release

[Felix Cheung]

I’d strongly recommend the community to move towards the first release with
the WIP disclaimer
https://incubator.apache.org/policy/incubation.html#work_in_progress_disclaimer

https://incubator.apache.org/policy/incubation.html#releases


As for the LGPL dependency specifically, a replacement will be needed?


On 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.org/legal/resolved.html#category-x)
>
> 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
>
> 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 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 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. In order to make it
> >> happen,
> >>
> >> Finalize coding and documentation before Dec 6:
> >> 1. I believe the Move-to-JTS PR will be done in around one week.
> >> 2. Then we can accept Pawel' Python RDD-DF Adapter PR, if necessary
> >> 3. I will work on Sedona documentation.
> >> 4. @Netanel will work on Sedona support of Spark 2.4 and Scala 2.11. I
> will
> >> first create a branch for it to illustrate some necessary changes in
> Sedona
> >> SQL for Spark 2.4.
> >>
> >> Final walk-through before Dec 13
> >> 1. Netanel can test the release management for Sedona.
> >> 2. Other committers can go through the docs, release notes
> >>
> >> Community voting before Dec 20
> >> 1. Sedona community voting: before Dec 16
> >> 2. Apache Incubator voting: before Dec 20
> >>
> >> Push to Maven Central and PyPi before Dec 24
> >>
> >> Please feel free to comment if you have any suggestions!
> >>
> >> Jia
> >>
> >> On Sun, Nov 22, 2020 at 9:51 AM Paweł Kociński <
> pawel93kocin...@gmail.com>
> >> wrote:
> >>
> >>> Hi,
> >>> I saw some users reported need to improve Python RDD API in two
> >> scenarios:
> >>> - converting spatial flat join result to df
> >>> - saving spatial flat join result directly to external storage
> >>>
> >>> Currently SerDe between jvm and Python causes additional time needed to
> >>> compute the result. I have a local 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 08:29 Jia Yu  napisał(a):
> >>>
> >>>> Dear all,
> >>>>
> >>>> Thanks for all your suggestions.
> >>>>
> >>>> 1. To completely solve the long-overdue JTS issue, I made a Sedona PR
> >> and
> >>>> two JTS PRs. @Jim Hughes  , @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
> >>>> https://github.com/locationtech/jts/pull/634
> >>>>
> >>>> 2. To move forward with the 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.
&g

Re: First Sedona release

[Felix Cheung]

This is a great cross community collaboration and fantastic outcome. Thank
you.


On Tue, Nov 17, 2020 at 11:33 AM Jia Yu  wrote:

> Dear all,
>
> According to my discussion with JTS committer Jim and Martin, both JTS PRs
> could be partially or completely avoided by adopting the following methods:
>
> 1. For Check UserData in Geometry Equals
> https://github.com/locationtech/jts/pull/633 , in Sedona RDD JoinQuery, I
> will try to use HashMap as an intermediate step because HashMap allows
> self-defined hash key. The new method will be added here:
>
> https://github.com/apache/incubator-sedona/blob/master/core/src/main/java/org/apache/sedona/core/spatialOperator/JoinQuery.java#L88
> 2. For Change Access Modifier and Add setter and getter
> https://github.com/locationtech/jts/pull/634 , I will add a
> package-private
> RTree/QuadTree class in Sedona, which should be under the same folder of
> JTS, to expose the internals of JTS indices.
>
> If both methods work, I believe we probably will not need to change JTS and
> can directly use JTS in Maven Centrl. I will try out the solutions in the
> next few days.
>
> Thanks,
> Jia
>
> On Mon, Nov 16, 2020 at 2:30 PM Jim Hughes  wrote:
>
> > Hi Jia,
> >
> > Thanks for putting up the PRs.  Martin and I have commented on them.  If
> > you are interested in a more real-time discussion than the PRs, Martin
> > and I are both in the JTS Gitter (https://gitter.im/locationtech/jts).
> >
> > To ask directly, please do not fork JTS.  You will be unable to publish
> > 1.16.2 artifacts on Maven central.  Finding another way to do this will
> > cause confusion.
> >
> > Cheers,
> >
> > Jim
> >
> > On 11/16/20 2:28 AM, Jia Yu wrote:
> > > Dear all,
> > >
> > > Thanks for all your suggestions.
> > >
> > > 1. To completely solve the long-overdue JTS issue, I made a Sedona PR
> and
> > > two JTS PRs. @Jim Hughes  , @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
> > > https://github.com/locationtech/jts/pull/634
> > >
> > > 2. To move forward with the 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 Malka   could you please do another
> > > dry-run on the Sedona first release on this Sedona branch:
> > sedona-1.0-doc:
> > > https://github.com/apache/incubator-sedona/tree/sedona-1.0-doc
> > >
> > > Thanks,
> > > Jia
> > >
> > > On Thu, Nov 12, 2020 at 11:36 AM Jim Hughes  wrote:
> > >
> > >> Hi Mo,
> > >>
> > >> I can definitely help.  The first step will be for Jia to push a PR
> for
> > >> the JTS changes.  (Since they are his changes, I cannot do this on his
> > >> behalf.)
> > >>
> > >>   From talking to the lead JTS developer, he wanted to see the
> previous
> > >> PR (from months/a year+ ago) split up.  I think the initial PR should
> be
> > >> used to discuss what changes are sensible for JTS and where we'll need
> > >> to push some of the changes to Sedona.
> > >>
> > >> Concretely, I noticed that the Sedona JTS fork changes the toString on
> > >> Geometry to include printing out the userData.  I imagine that may
> cause
> > >> trouble for downstream JTS users, so it'd be good to find an
> > >> alternative.  One suggestion would to be add a static method in Sedona
> > >> for printing a Geometry with its userData object.
> > >>
> > >> Cheers,
> > >>
> > >> Jim
> > >>
> > >> On 11/12/20 12:32 PM, Mohamed Sarwat wrote:
> > >>> Folks,
> > >>>
> > >>> I totally agree with Jim on that. Jim, would you like to take the
> lead
> > >> on that - I trust that you can bring this task to completion. Jia,
> would
> > >> you please let us know how we can incorporate the changes into the JTS
> > >> master branch?
> > >>> Thanks,
> > >>>
> > >>>> On Nov 12, 2020, at 10:10 AM, Jim Hughes  wrote:
> > >>>>
> > >>>>

Re: JTS 1.16.2

[Felix Cheung]

I believe this is the jts discussion in the other thread.

On Mon, Nov 16, 2020 at 12:54 PM Netanel Malka  wrote:

> Hi Jia,
> I tried to use the branch sedona-1.0-doc but the artifact for 1.16.2 is
> not in the Maven Central so I cannot compile the project.
>
> I got:
> The POM for org.locationtech.jts:jts-core:jar:1.16.2 is missing, no
> dependency information available
>
> I searched for the artifact here:
> https://mvnrepository.com/artifact/org.locationtech.jts/jts-core
> And also in the JCenter repo here:
>
> https://bintray.com/bintray/jcenter/org.locationtech.jts%3Ajts-core#files/org/locationtech/jts/jts-core
>
> As you can see there is no artifact for 1.16.2 only for 1.16.1 or 1.17.x
>
> Can you downgrade to 1.16.1 or upgrade to 1.17.1?
>
> Thanks.
>

Re: Support Spark 2.4 in Sedona 1.0

[Felix Cheung]

You might be able to create shim and build in profile
Like
https://github.com/graphframes/graphframes/tree/branch-0.5/src/main


On Thu, Nov 12, 2020 at 3:23 PM Jia Yu  wrote:

> In order to support Spark 2.4, Sedona needs to use different logic for SQL
> aggregation functions. I am not sure if this could be achieved by using
> different profiles.
>
> Sedona for Spark 3.0:
> https://github.com/apache/incubator-sedona/blob/master/sql/src/main/scala/org/apache/spark/sql/sedona_sql/expressions/AggregateFunctions.scala
> Sedona for Spark 2.4:
> https://github.com/apache/incubator-sedona/blob/spark-2.3-2.4/sql/src/main/scala/org/apache/spark/sql/geosparksql/expressions/AggregateFunctions.scala
>
> On Thu, Nov 12, 2020 at 9:42 AM Mo Sarwat  wrote:
>
>> Yes, I believe we still need to support Spark 2.4 since  many Sedona users
>> are still using it
>>
>> On Wed, Nov 11, 2020 at 11:21 PM Netanel Malka 
>> wrote:
>>
>> > What do you mean by compile target?
>> >
>> > ?
>> >
>> > Iv'e found Apache Zeppelin handle multiple Spark versions here using
>> > profile for each Spark version:
>> >
>> > https://github.com/apache/zeppelin/blob/master/spark/pom.xml#L185
>> >
>> >
>> > Do you think this method is better?
>> >
>> >
>> >
>> > Netanel Malka,
>> > Big Data Consultant
>> > [Description: Description: Description: Description:
>> > cid:image001.jpg@01C85203.36A2AF30]
>> > 
>> > From: Felix Cheung 
>> > Sent: Thursday, November 12, 2020 04:05
>> > To: dev@sedona.apache.org
>> > Cc: Jinxuan Wu; Mohamed Sarwat; Netanel Malka; Paweł Kociński; Zongsi
>> > Zhang; d...@sedona.incubator.apache.org
>> > Subject: Re: Support Spark 2.4 in Sedona 1.0
>> >
>> > I am not sure it should be a branch? It is common to deal with this as a
>> > compile target, not as a separate branch. A separate branch might have
>> > difficulty to release?
>> >
>> > There are a few example in projects where they handle multiple Spark
>> > target version like this.
>> >
>> >
>> > On Wed, Nov 11, 2020 at 12:56 PM Jia Yu > > ji...@apache.org>> wrote:
>> > OK. I agree. I am gonna create a branch for spark-2.3/2.4. Regarding the
>> > compiler used in each branch,
>> >
>> > For Sedona on Spark 3.0, I will compile it using Scala 2.12
>> > For Sedona on Spark 2.4, I will compile it using Scala 2.11.
>> >
>> > For the Java code in both branches, I will compile them using Java 1.8
>> >
>> > Am I missing anything here?
>> >
>> >
>> > On Wed, Nov 11, 2020 at 7:31 AM Netanel Malka > > > netan...@sela.co.il>> wrote:
>> >
>> > > Hi,
>> > >
>> > > I also think that we need to support 2.4.
>> > >
>> > > I saw that even Apache Spark still releases 2.4.x artifacts. (2.4.7
>> Sep
>> > > 12, 2020)
>> > >
>> > > I also asked about it on *us...@spark.apache.org> > us...@spark.apache.org> > > us...@spark.apache.org>>*
>> > >  :
>> > >
>> > >
>> > > *Sean Owen (answered the question): *
>> > >
>> > > "I don't think there's an official EOL for Spark 2.4.x but would
>> expect
>> > > another maintenance release in the first half of 2021 at least. I'd
>> also
>> > > guess it wouldn't be maintained by 2022."
>> > >
>> > >
>> > > ?BR,
>> > >
>> > >
>> > >
>> > > Netanel Malka,
>> > > Big Data Consultant
>> > > [image: Description: Description: Description: Description:
>> > > cid:image001.jpg@01C85203.36A2AF30]
>> > > --
>> > > *From:* Paweł Kociński > > pawel93kocin...@gmail.com>>
>> > > *Sent:* Wednesday, November 11, 2020 00:29
>> > > *To:* Jia Yu
>> > > *Cc:* dev@sedona.apache.org<mailto:dev@sedona.apache.org>;
>> > d...@sedona.incubator.apache.org<mailto:d...@sedona.incubator.apache.org
>> >;
>> > Jinxuan Wu;
>> > > Mohamed Sarwat; Netanel Malka; Zongsi Zhang
>> > > *Subject:* Re: Support Spark 2.4 in Sedona 1.0
>> > >
>> > > Hi Jia,
>> > > I think we should support spark 2.4, a lot of users still use it. More
>> > > than that I think more users still have jobs writt

Re: [VOTE] Release Apache Pinot (incubating) 0.6.0 RC1

[Felix Cheung]

It was discussed several times in private@pinot, we can take it from there.

It will probably best if one of you simply edit that line right now in the
git repo so we don’t get into this again in 0.7 release.


On Wed, Nov 11, 2020 at 10:58 AM Jialiang Li  wrote:

> Hi Felix,
>
> Thanks for the feedback! Sorry I don't have the context on including
> thirdeye into the pinot open source release. Could you share the related
> email thread? If it's not urgent, maybe we can add some notes in pinot
> release page (https://github.com/apache/incubator-pinot/releases), so
> that the next POC will pick it up.
>
> Thanks,
> Jack
>
> On 2020/11/11 04:05:49, Felix Cheung  wrote:
> > +1 but
> >
> > it was discussed before, but thirdeye is not included in the source
> release
> >
> https://github.com/apache/incubator-pinot/blob/master/pinot-distribution/pinot-source-assembly.xml#L39
> >
> > - incubating in name
> > - signature and hash fine
> > - DISCLAIMER is fine
> > - LICENSE and NOTICE are fine
> > - No unexpected binary files
> > Event for testing, ideally you want to build the test tarball from
> > source paddingPercent.tar.gz, paddingOld.tar.gz, paddingNull.tar.gz,
> > fake_stream_avro_data.tar.gz
> > - All source files have ASF headers
> >
> > On Tue, Nov 10, 2020 at 5:29 PM Jialiang Li  wrote:
> >
> > > Hi all,
> > >
> > > This is a call for vote to the release Apache Pinot (incubating)
> version
> > > 0.6.0.
> > >
> > > Apache Pinot (incubating) is a distributed columnar storage engine
> that can
> > > ingest
> > > data in realtime and serve analytical queries at low latency.
> > >
> > > Pinot community has voted and approved this release.
> > >
> > > Vote thread:
> > >
> > >
> https://lists.apache.org/thread.html/r9c715527f12e425ee15024cdbae7b597c04942a8901711f521f53a34%40%3Cdev.pinot.apache.org%3E
> > >
> > > Result thread:
> > >
> > >
> https://lists.apache.org/thread.html/r646618892a671155fe810c945c7e16f2ad1de7d7c92bc9e24c0a3290%40%3Cdev.pinot.apache.org%3E
> > >
> > > The release candidate:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.6.0-rc1
> > >
> > > Git tag for this release:
> > > https://github.com/apache/incubator-pinot/tree/release-0.6.0-rc1
> > >
> > > Git hash for this release:
> > > bb646baceafcd9b849a1ecdec7a11203c7027e21
> > >
> > > The artifacts have been signed with key: FC4005F4DCB8B2F4, which can be
> > > found in the following KEYS file.
> > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> > >
> > > Release notes:
> > >
> https://github.com/apache/incubator-pinot/releases/tag/release-0.6.0-rc1
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/orgapachepinot-1022
> > >
> > > Documentation on verifying a release candidate:
> > >
> > >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> > >
> > >
> > > The vote will be open for at least 72 hours or until necessary number
> of
> > > votes are reached.
> > >
> > > Please vote accordingly,
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thanks,
> > > Apache Pinot (incubating) team
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Support Spark 2.4 in Sedona 1.0

[Felix Cheung]

I am not sure it should be a branch? It is common to deal with this as a
compile target, not as a separate branch. A separate branch might have
difficulty to release?

There are a few example in projects where they handle multiple Spark target
version like this.


On Wed, Nov 11, 2020 at 12:56 PM Jia Yu  wrote:

> OK. I agree. I am gonna create a branch for spark-2.3/2.4. Regarding the
> compiler used in each branch,
>
> For Sedona on Spark 3.0, I will compile it using Scala 2.12
> For Sedona on Spark 2.4, I will compile it using Scala 2.11.
>
> For the Java code in both branches, I will compile them using Java 1.8
>
> Am I missing anything here?
>
>
> On Wed, Nov 11, 2020 at 7:31 AM Netanel Malka  wrote:
>
> > Hi,
> >
> > I also think that we need to support 2.4.
> >
> > I saw that even Apache Spark still releases 2.4.x artifacts. (2.4.7 Sep
> > 12, 2020)
> >
> > I also asked about it on *us...@spark.apache.org  >*
> >  :
> >
> >
> > *Sean Owen (answered the question): *
> >
> > "I don't think there's an official EOL for Spark 2.4.x but would expect
> > another maintenance release in the first half of 2021 at least. I'd also
> > guess it wouldn't be maintained by 2022."
> >
> >
> > ​BR,
> >
> >
> >
> > Netanel Malka,
> > Big Data Consultant
> > [image: Description: Description: Description: Description:
> > cid:image001.jpg@01C85203.36A2AF30]
> > --
> > *From:* Paweł Kociński 
> > *Sent:* Wednesday, November 11, 2020 00:29
> > *To:* Jia Yu
> > *Cc:* dev@sedona.apache.org; d...@sedona.incubator.apache.org; Jinxuan
> Wu;
> > Mohamed Sarwat; Netanel Malka; Zongsi Zhang
> > *Subject:* Re: Support Spark 2.4 in Sedona 1.0
> >
> > Hi Jia,
> > I think we should support spark 2.4, a lot of users still use it. More
> > than that I think more users still have jobs written in spark 2.4 than
> > 3.0.  We will use an additional branch for that use case ? I mean Spark
> 2.4
> > with scala 2.12 is important one.
> > Regards,
> > Paweł
> >
> > pon., 9 lis 2020 o 20:44 Jia Yu  napisał(a):
> >
> >> Dear all,
> >>
> >> In Sedona 1.0, we definitely will support Spark 3.0. But I wonder
> whether
> >> we should support Spark 2.4.
> >>
> >> In order to support Spark 2.4, we need to do the following
> >>
> >> 1. Compile the source using Scala 2.11. Sedona master branch currently
> is
> >> compiled by Scala 2.12 and Java 1.8
> >> 2. For the Scala code of Sedona-SQL and Viz-SQL, I need to change the
> (1)
> >> UDF registration hook (2) the SQL aggregation function format
> >> 3. In the future releases of Sedona, use git cherry-pick to pick
> >> important features back to the Spark 2.4 branch. This is what I did in
> >> GeoSpark to support Spark 2.1, 2.2, 2.3
> >>
> >> GeoSpark 1.2.0 - 1.3.1 support Spark 2.4 already. We can simply leave it
> >> that way and just support Spark 3.0.
> >>
> >> Do you think we should support Spark 2.4 in the future release?
> >>
> >> Thanks,
> >> Jia Yu
> >>
> >
>

Re: [VOTE] Release Apache Pinot (incubating) 0.6.0 RC1

[Felix Cheung]

+1 but

it was discussed before, but thirdeye is not included in the source release
https://github.com/apache/incubator-pinot/blob/master/pinot-distribution/pinot-source-assembly.xml#L39

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
Event for testing, ideally you want to build the test tarball from
source paddingPercent.tar.gz, paddingOld.tar.gz, paddingNull.tar.gz,
fake_stream_avro_data.tar.gz
- All source files have ASF headers

On Tue, Nov 10, 2020 at 5:29 PM Jialiang Li  wrote:

> Hi all,
>
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.6.0.
>
> Apache Pinot (incubating) is a distributed columnar storage engine that can
> ingest
> data in realtime and serve analytical queries at low latency.
>
> Pinot community has voted and approved this release.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/r9c715527f12e425ee15024cdbae7b597c04942a8901711f521f53a34%40%3Cdev.pinot.apache.org%3E
>
> Result thread:
>
> https://lists.apache.org/thread.html/r646618892a671155fe810c945c7e16f2ad1de7d7c92bc9e24c0a3290%40%3Cdev.pinot.apache.org%3E
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.6.0-rc1
>
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.6.0-rc1
>
> Git hash for this release:
> bb646baceafcd9b849a1ecdec7a11203c7027e21
>
> The artifacts have been signed with key: FC4005F4DCB8B2F4, which can be
> found in the following KEYS file.
> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
>
> Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.6.0-rc1
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1022
>
> Documentation on verifying a release candidate:
>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly,
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache Pinot (incubating) team
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Superset (incubating) 0.38.0 based on Superset 0.38.0rc3

[Felix Cheung]

+1 binding

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers


From: Jim Jagielski 
Sent: Saturday, November 7, 2020 9:56:55 AM
To: dev@superset.apache.org 
Subject: Re: [VOTE] Release Apache Superset (incubating) 0.38.0 based on 
Superset 0.38.0rc3

+1 (binding)

> On Nov 6, 2020, at 6:14 AM, daniel gaspar  wrote:
>
> Hello Superset Community,
>
> This is a call for the vote to release Apache Superset
> (incubating) version 0.38.0.
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.38.0rc3/
>
> Git tag for the release:
> https://github.com/apache/incubator-superset/tree/0.38.0rc3
>
> The Change Log for the release:
> https://github.com/apache/incubator-superset/blob/0.38.0rc3/CHANGELOG.md
>
> The Updating instructions for the release:
> https://github.com/apache/incubator-superset/blob/0.38.0rc3/UPDATING.md
>
> public keys are available at:
>
> https://www.apache.org/dist/incubator/superset/KEYS
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Superset (Incubating) Team

Re: Long queue time on travis-ci

[Felix Cheung]

Hello,

There has been, in the past, incidents where the shared Travis resource is
exhausted.

It might help if you restrict to build one branch (like main) only.

Some projects have acquired corporate sponsorship for a separate Travis
instance.

Some has moved to another system, like GitHub Action (eg superset or
airflow)
https://cwiki.apache.org/confluence/display/INFRA/Github+Actions+to+DockerHub
(I am not certain if there is any fee involved)

ASF has no policy against using other CI or test system.


On Sun, Nov 8, 2020 at 11:23 AM Jia Yu  wrote:

> Hi Felix,
>
> I notice that recently, the Travis-CI auto-build on our PRs and commits
> seem to have a very long queue time (
> https://travis-ci.org/github/apache/incubator-sedona/builds/742278311)
>
> Is this because we are under Apache organization and there are hundreds of
> builds going on? Or is this because the build is based on a non-master
> branch? If we push the commit to the master branch, will the build be
> faster?
>
> Thanks,
> Jia
>

Re: First Sedona release

[Felix Cheung]

Great progress!

To add,
A) I’d strongly recommend the WIP disclaimer - it would be much easier to
pass with in the first release
https://incubator.apache.org/policy/incubation.html#disclaimers

B) more info in signing, checksum
https://infra.apache.org/release-signing.html

C) signing key should be individual’s and (public key ) published and also
listed in KEYS file - KEYS file  should be located next to the staging (and
later release) location, see above

D) “correct place” - this is in reference to ASF officIal staging server
http://www.apache.org/legal/release-policy.html#stage
And can be “uploaded” by committing to svn
http://www.apache.org/legal/release-policy.html#upload-ci

E) python / PyPI -
https://incubator.apache.org/guides/distribution.html#pypi



On Sun, Nov 1, 2020 at 2:17 PM Jia Yu  wrote:

> 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
> , 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  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
> >
>

Re: Podling Sedona Report Reminder - November 2020

[Felix Cheung]

Reminder.


From: jmcl...@apache.org 
Sent: Friday, October 23, 2020 10:54:49 PM
To: d...@sedona.incubator.apache.org 
Subject: 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 the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, November 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/November2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: [VOTE] Graduate Apache TVM as TLP

[Felix Cheung]

+1 binding


On Thu, Oct 22, 2020 at 7:21 AM Timothy Chen  wrote:

> +1 binding as well
>
> Tim
>
> Sent via Superhuman iOS 
>
>
> On Wed, Oct 21 2020 at 08:18, Sebastian Schelter  wrote:
>
> >
> > +1
> >
> > On 2020/10/19 17:29:23, Tianqi Chen  wrote:
> >
> > Dear Incubator:
> >
> > A month ago we brought up the discussion about graduating TVM as TLP.
> > After great discussions in the apache way [2],
> > we get good support from the incubator and also get helpful feedback
> about
> > producing another release.
> > The TVM PPMC always focused on getting consensus, and is fully committed
> > to building a better community,
> > as a result, we decided to withdraw the graduation until there has been
> > another release.
> >
> > Now that the community has produced another release by two new release
> > managers from different organizations
> > and a after new round of discussion[1], we propose to formally vote on
> > TVM's graduation.
> >
> > Please also see the community discussion thread[3], voting thread[4].
> >
> > This is a formal voting thread about Apache TVM's graduation, please
> Vote:
> > [ ] +1 - Recommend graduation of Apache TVM as a TLP
> > [ ] 0 - I don't feel strongly about it, but don't object
> > [ ] -1 - Do not recommend graduation of Apache TVM because...
> >
> > The VOTE will open for at least 72 hours.
> >
> > --
> > Summary of community status:
> >
> > Compliance
> >
> > Compliance is what every project is required to do. These policies are
> set
> > to protect Apache’s brand,
> > encourage community over code and set a common foundation for the
> > projects. Usually compliance is well documented (as per-apache way, what
> is
> > not documented did not happen).
> > The TVM PPMC has been diligently upholding compliances, including, but
> not
> > limited to
> >
> > - T0 Project website hosted at ASF https://tvm.apache.org/.
> > - T1 Produce apache release, no cat-X code.
> > - T2 No advertising non-release items as Apache release.
> > - T3 Protect Apache brand, working with trademark to resolve branding
> > concerns.
> > - T4 Clearly marks third party artifacts and makes sure they comply with
> > trademark policies.
> > - T5 Open development: everyone happens (also) happens on dev@
> > - T6 Consider all forms of contributions for committer nomination.
> > - T7 Make sure release processes are clearly documented, reproducible by
> > any committers.
> >
> > Community
> >
> > The “community over code” is one of the most important factors of the
> > Apache way.
> > The TVM PPMC has been working very hard to foster a healthy, diverse and
> > independent community,
> > and will continue to do so.
> >
> > - C0: Consider all forms of contributions as merit.
> > - C1: Encourage community diversity by only nominating people from
> > different organizations.
> > - C2: Actively discusses, and brings in new committers from diverse
> > backgrounds.
> > The community grows healthily and is quite vibrant.
> >
> > -
> >
> > Establish the Apache TVM Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> a
> > Project Management Committee charged with the creation and maintenance of
> > open-source software, for distribution at no charge to the public,
> related
> > to compilation of machine learning models to run on a wide range of
> > hardware platforms...
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache TVM Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache TVM Project be and hereby is responsible for
> the
> > creation and maintenance of software related to compilation of machine
> > learning models to run on a wide range of hardware platforms; and be it
> > further
> >
> > RESOLVED, that the office of "Vice President, Apache TVM" be and hereby
> is
> > created, the person holding such office to serve at the direction of the
> > Board of Directors as the chair of the Apache TVM Project, and to have
> > primary responsibility for management of the projects within the scope of
> > responsibility of the Apache TVM Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache TVM Project:
> >
> > * Tianqi Chen 
> > * Timothy Chen 
> > * Zhi Chen 
> > * Byung-Gon Chun 
> > * Ziheng Jiang 
> > * Furkan Kamaci 
> > * YiZhi Liu 
> > * Masahiro Masuda 
> > * Thierry Moreau 
> > * Jared Roesch 
> > * Henry Saputra 
> > * Haichen Shen 
> > * Markus Weimer 
> > * Eddie Yan 
> > * Lianmin Zheng 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
> > the office of Vice President, Apache TVM, to serve in accordance with and
> > subject to the direction of the 

Re: [VOTE] Graduate Apache Superset (incubating) as a Top Level Project

[Felix Cheung]

+1

;)

On Tue, Oct 20, 2020 at 2:31 AM Justin Mclean 
wrote:

> HI,
>
> +1 (binding)
>
> Thanks for addressing everything I brought up here and on your private
> list. There's still a little more to do, but it’s being dealt with, so I’m
> all good with you graduating. Do keep an eye on how you are handling those
> synchronous meetings and try to make sure everyone can contribute and
> information is brought back to the list.
>
> Congratulations!
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [Draft] Zeppelin Board report Oct 2020

[Felix Cheung]

Looks good

On Wed, Oct 14, 2020 at 9:01 PM Jeff Zhang  wrote:

> +1, Thanks moon
>
> moon soo Lee  于2020年10月15日周四 上午11:58写道：
>
>> Hi Folks,
>>
>> Since the report due date is 14/Oct, I made a draft of it.
>> Please review this.
>>
>> ## Description:
>>
>>  -  Apache Zeppelin is a collaborative data analytics and visualization
>> tool
>> for general-purpose data processing systems.
>>
>> ## Activity:
>>
>>  - 0.9.0-preview2 has released. Now we are planning the release of 0.9.0.
>>
>> ## Health report:
>>
>>  - +6 new code contributors since last report. 329 total.
>>
>> ## PMC changes:
>>
>>  - There are currently 22 committers and 11 PMC members in this project.
>> The Committer-to-PMC ratio is 2:1.
>>  - Last PMC addition was Jeff Zhang on Thu Jan 25 2018
>>  - We invited a new PMC member, but wait for his response.
>>
>> ## Committer base changes:
>>
>>  - Currently 22 committers.
>>  - Last committer addition was Philipp Dallig on 2020-06-24
>>
>> ## Releases:
>>
>>  - 0.9.0-preview2 was released on July 27, 2020
>>  - 0.9.0-preview1 was released on March 26, 2020
>>  - 0.8.2 was released on Wed Sep 29 2019
>>  - 0.8.1 was released on Wed Jan 23 2019
>>  - 0.8.0 was released on Wed Jul 18 2018
>>
>>
>> ## Mailing list activity:
>>
>>  - us...@zeppelin.apache.org:
>> - 92 emails sent to list ( 173 in previous quarter)
>>
>> - dev@zeppelin.apache.org:
>> - 777 emails sent to list ( 774 in previous quarter)
>>
>> ## JIRA activity:
>>
>>  - 132 JIRA tickets created in the last 3 months
>>  - 88 JIRA tickets are closed in last 3 months.
>>
>
>
> --
> Best Regards
>
> Jeff Zhang
>

Re: Podling Sedona Report Reminder - October 2020

[Felix Cheung]

Thx

On Mon, Oct 5, 2020 at 10:42 PM Jia Yu  wrote:

> Yes, indeed. I am not sure why. I copied the content back and now it has
> all sections and text.
>
> On Mon, Oct 5, 2020 at 8:39 PM Felix Cheung 
> wrote:
>
> > Thanks- it looks like the report is truncated? It seems to be missing
> some
> > text and section
> >
> >
> > On Sun, Oct 4, 2020 at 11:53 PM Jia Yu  wrote:
> >
> > > Hi folks,
> > >
> > > I have submitted the draft of the report. Please take a look. Mentors,
> > > thank you very much for your help!
> > >
> > > Jia
> > >
> > > On Sat, Oct 3, 2020 at 5:31 PM Jia Yu  wrote:
> > >
> > > > Hi Felix,
> > > >
> > > > I will write the report tomorrow. I will let you guys know once I am
> > > done.
> > > >
> > > > Thanks,
> > > > Jia
> > > >
> > > > On Sat, Oct 3, 2020 at 5:18 PM Felix Cheung 
> > > > wrote:
> > > >
> > > >> Any volunteer for this report?
> > > >>
> > > >>
> > > >>
> > > >> On Sat, Sep 19, 2020 at 6:07 PM  wrote:
> > > >>
> > > >> > 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, 21 October 2020.
> > > >> > The report for your podling will form a part of the Incubator PMC
> > > >> > report. The Incubator PMC requires your report to be submitted 2
> > weeks
> > > >> > before the board meeting, to allow sufficient time for review and
> > > >> > submission (Wed, October 07).
> > > >> >
> > > >> > Please submit your report with sufficient time to allow the
> > Incubator
> > > >> > PMC, and subsequently board members to review and digest. Again,
> the
> > > >> > very latest you should submit your report is 2 weeks prior to the
> > > board
> > > >> > meeting.
> > > >> >
> > > >> > Candidate names should not be made public before people are
> actually
> > > >> > elected, so please do not include the names of potential
> committers
> > or
> > > >> > PPMC members in your report.
> > > >> >
> > > >> > Thanks,
> > > >> >
> > > >> > The Apache Incubator PMC
> > > >> >
> > > >> > Submitting your Report
> > > >> >
> > > >> > --
> > > >> >
> > > >> > Your report should contain the following:
> > > >> >
> > > >> > *   Your project name
> > > >> > *   A brief description of your project, which assumes no
> knowledge
> > of
> > > >> > the project or necessarily of its field
> > > >> > *   A list of the three most important issues to address in the
> move
> > > >> > towards graduation.
> > > >> > *   Any issues that the Incubator PMC or ASF Board might wish/need
> > to
> > > be
> > > >> > aware of
> > > >> > *   How has the community developed since the last report
> > > >> > *   How has the project developed since the last report.
> > > >> > *   How does the podling rate their own maturity.
> > > >> >
> > > >> > This should be appended to the Incubator Wiki page at:
> > > >> >
> > > >> > https://cwiki.apache.org/confluence/display/INCUBATOR/October2020
> > > >> >
> > > >> > Note: This is manually populated. You may need to wait a little
> > before
> > > >> > this page is created from a template.
> > > >> >
> > > >> > Note: The format of the report has changed to use markdown.
> > > >> >
> > > >> > Mentors
> > > >> > ---
> > > >> >
> > > >> > Mentors should review reports for their project(s) and sign them
> off
> > > on
> > > >> > the Incubator wiki page. Signing off reports shows that you are
> > > >> > following the project - projects that are not signed may raise
> > alarms
> > > >> > for the Incubator PMC.
> > > >> >
> > > >> > Incubator PMC
> > > >> >
> > > >>
> > > >
> > >
> >
>

Re: Podling Sedona Report Reminder - October 2020

[Felix Cheung]

Thanks- it looks like the report is truncated? It seems to be missing some
text and section


On Sun, Oct 4, 2020 at 11:53 PM Jia Yu  wrote:

> Hi folks,
>
> I have submitted the draft of the report. Please take a look. Mentors,
> thank you very much for your help!
>
> Jia
>
> On Sat, Oct 3, 2020 at 5:31 PM Jia Yu  wrote:
>
> > Hi Felix,
> >
> > I will write the report tomorrow. I will let you guys know once I am
> done.
> >
> > Thanks,
> > Jia
> >
> > On Sat, Oct 3, 2020 at 5:18 PM Felix Cheung 
> > wrote:
> >
> >> Any volunteer for this report?
> >>
> >>
> >>
> >> On Sat, Sep 19, 2020 at 6:07 PM  wrote:
> >>
> >> > 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, 21 October 2020.
> >> > The report for your podling will form a part of the Incubator PMC
> >> > report. The Incubator PMC requires your report to be submitted 2 weeks
> >> > before the board meeting, to allow sufficient time for review and
> >> > submission (Wed, October 07).
> >> >
> >> > Please submit your report with sufficient time to allow the Incubator
> >> > PMC, and subsequently board members to review and digest. Again, the
> >> > very latest you should submit your report is 2 weeks prior to the
> board
> >> > meeting.
> >> >
> >> > Candidate names should not be made public before people are actually
> >> > elected, so please do not include the names of potential committers or
> >> > PPMC members in your report.
> >> >
> >> > Thanks,
> >> >
> >> > The Apache Incubator PMC
> >> >
> >> > Submitting your Report
> >> >
> >> > --
> >> >
> >> > Your report should contain the following:
> >> >
> >> > *   Your project name
> >> > *   A brief description of your project, which assumes no knowledge of
> >> > the project or necessarily of its field
> >> > *   A list of the three most important issues to address in the move
> >> > towards graduation.
> >> > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> be
> >> > aware of
> >> > *   How has the community developed since the last report
> >> > *   How has the project developed since the last report.
> >> > *   How does the podling rate their own maturity.
> >> >
> >> > This should be appended to the Incubator Wiki page at:
> >> >
> >> > https://cwiki.apache.org/confluence/display/INCUBATOR/October2020
> >> >
> >> > Note: This is manually populated. You may need to wait a little before
> >> > this page is created from a template.
> >> >
> >> > Note: The format of the report has changed to use markdown.
> >> >
> >> > Mentors
> >> > ---
> >> >
> >> > Mentors should review reports for their project(s) and sign them off
> on
> >> > the Incubator wiki page. Signing off reports shows that you are
> >> > following the project - projects that are not signed may raise alarms
> >> > for the Incubator PMC.
> >> >
> >> > Incubator PMC
> >> >
> >>
> >
>

Re: Podling Sedona Report Reminder - October 2020

[Felix Cheung]

Any volunteer for this report?



On Sat, Sep 19, 2020 at 6:07 PM  wrote:

> 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, 21 October 2020.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, October 07).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/October2020
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: "Issues" mailing is not available?

[Felix Cheung]

Maybe it is moderation? Although I don’t think I’ve seen any mail that is
pending moderation.

But generally we can have discussion in dev@

issues@ in a lot of projects are dedicated only for JIRA updates (which
could be a lot)


On Thu, Oct 1, 2020 at 7:38 PM Jia Yu  wrote:

> Hello Felix,
>
> Several users reported that the issues@sedona.apache.org is not a valid
> email address or their email didn't appear in the mailing list. But it
> looks like I can still post emails to this mailing list.
> https://lists.apache.org/list.html?issues@sedona.apache.org
>
> Do you know whether there is anything wrong with the mailing list?
>
> Thanks,
> Jia
>
>

Re: "Issues" mailing is not available?

[Felix Cheung]

Maybe it is moderation? Although I don’t think I’ve seen any mail that is
pending moderation.

But generally we can have discussion in dev@

issues@ in a lot of projects are dedicated only for JIRA updates (which
could be a lot)


On Thu, Oct 1, 2020 at 7:38 PM Jia Yu  wrote:

> Hello Felix,
>
> Several users reported that the iss...@sedona.apache.org is not a valid
> email address or their email didn't appear in the mailing list. But it
> looks like I can still post emails to this mailing list.
> https://lists.apache.org/list.html?iss...@sedona.apache.org
>
> Do you know whether there is anything wrong with the mailing list?
>
> Thanks,
> Jia
>
>

Re: [VOTE] Release Apache Superset (incubating) version 0.37.2

[Felix Cheung]

+1 (binding)

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers
- did not compile


On Fri, Sep 25, 2020 at 11:31 PM Furkan KAMACI 
wrote:

> Hi,
>
>
>
> +1 (binding, carrying over my vote).
>
>
>
> Kind Regards,
>
> Furkan KAMACI
>
>
>
> On Thu, Sep 24, 2020 at 7:13 PM Ville Brofeldt  >
>
> wrote:
>
>
>
> > Hello IPMC,
>
> >
>
> > The Apache Superset (incubating) community has voted on and approved a
>
> > proposal to
>
> > release Apache Superset (incubating) version 0.37.2.
>
> > The voting thread can be found here:
>
> >
> https://mail-archives.apache.org/mod_mbox/superset-dev/202009.mbox/%3C18DE5EC6-6538-4C7F-86DC-6F6D46C07758%40gmail.com%3E
>
> >
>
> > Here are the binding +1 votes from mentors/IPMC members, carrying over
>
> > from the podling vote:
>
> > - Jim (mentor)
>
> > - Furkan (IPMC)
>
> >
>
> > We now kindly request the Incubator PMC members review and vote on this
>
> > incubator release.
>
> >
>
> > Apache Superset (incubating) is a modern, enterprise-ready business
>
> > intelligence web application
>
> >
>
> > The release candidate:
>
> > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.2rc2/
>
> >
>
> > Git tag for the release:
>
> > https://github.com/apache/incubator-superset/tree/0.37.2rc2
>
> >
>
> > The Change Log for the release:
>
> > https://github.com/apache/incubator-superset/blob/0.37.2rc2/CHANGELOG.md
>
> >
>
> > public keys are available at:
>
> >
>
> > https://www.apache.org/dist/incubator/superset/KEYS
>
> >
>
> > The vote will be open for at least 72 hours or until the necessary number
>
> > of votes are reached.
>
> >
>
> > Please vote accordingly:
>
> >
>
> > [ ] +1 approve
>
> > [ ] +0 no opinion
>
> > [ ] -1 disapprove with the reason
>
> >
>
> > Thanks,
>
> > The Apache Superset (Incubating) Team
>
>

Re: [VOTE] Release Apache Superset (incubating) version 0.37.1

[Felix Cheung]

+1

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers


On Wed, Sep 9, 2020 at 8:37 AM Ville Brofeldt 
wrote:

> Hello IPMC,
>
> The Apache Superset (incubating) community has voted on and approved a
> proposal to
> release Apache Superset (incubating) version 0.37.1.
> The voting thread can be found here:
> https://lists.apache.org/thread.html/r4462440505c3eea8fbfdbad76575d29a6ce23e7fb575d45a66a1e946%40%3Cdev.superset.apache.org%3E
> 
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Superset (incubating) is a modern, enterprise-ready business
> intelligence web application
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.1rc1/
>
> Git tag for the release:
> https://github.com/apache/incubator-superset/tree/0.37.1rc1
>
> The Change Log for the release:
> https://github.com/apache/incubator-superset/blob/0.37.1rc1/CHANGELOG.md
>
> public keys are available at:
> https://www.apache.org/dist/incubator/superset/KEYS
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Superset (Incubating) Team
>

Re: Podling Superset Report Reminder - September 2020

[Felix Cheung]

Great - I did 2 days ago.


From: Maxime Beauchemin 
Sent: Wednesday, September 2, 2020 9:19:17 AM
To: dev@superset.apache.org 
Subject: Re: Podling Superset Report Reminder - September 2020

Thank you Junlin for authoring the report this quarter.

@Felix we'd love if you could review and sign off on the report!

Max

On Tue, Sep 1, 2020 at 9:39 PM Junlin Chen  wrote:

> Dear mentors,
>
> Quarterly report has been submitted. Please let us know if you have any
> questions. Thank you!
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/September2020#superset
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/September2020#superset
> >
>
> Best,
> Junlin
>
>
>
> On 2020/08/27 01:55:52, jm...@apache.org wrote:
> > 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, 16 September 2020.>
> > The report for your podling will form a part of the Incubator PMC>
> > report. The Incubator PMC requires your report to be submitted 2 weeks>
> > before the board meeting, to allow sufficient time for review and>
> > submission (Wed, September 02).>
> >
> > Please submit your report with sufficient time to allow the Incubator>
> > PMC, and subsequently board members to review and digest. Again, the>
> > very latest you should submit your report is 2 weeks prior to the board>
> > meeting.>
> >
> > Candidate names should not be made public before people are actually>
> > elected, so please do not include the names of potential committers or>
> > PPMC members in your report.>
> >
> > Thanks,>
> >
> > The Apache Incubator PMC>
> >
> > Submitting your Report>
> >
> > -->
> >
> > Your report should contain the following:>
> >
> > *   Your project name>
> > *   A brief description of your project, which assumes no knowledge of>
> > the project or necessarily of its field>
> > *   A list of the three most important issues to address in the move>
> > towards graduation.>
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> be>
> > aware of>
> > *   How has the community developed since the last report>
> > *   How has the project developed since the last report.>
> > *   How does the podling rate their own maturity.>
> >
> > This should be appended to the Incubator Wiki page at:>
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/September2020>
> >
> > Note: This is manually populated. You may need to wait a little before>
> > this page is created from a template.>
> >
> > Note: The format of the report has changed to use markdown.>
> >
> > Mentors>
> > --->
> >
> > Mentors should review reports for their project(s) and sign them off on>
> > the Incubator wiki page. Signing off reports shows that you are>
> > following the project - projects that are not signed may raise alarms>
> > for the Incubator PMC.>
> >
> > Incubator PMC>
> >

Re: Progresso of the initial setup

[Felix Cheung]

Great. Do you mean issue should go to JIRA? issues@ should just be a feed
of JIRA


On Mon, Sep 7, 2020 at 3:14 AM Jia Yu  wrote:

> Hello all,
>
> 1. Sedona website has been moved to http://sedona.apache.org/ It is still
> using the old content for now. The new website will come soon.
>
> 2. GitHub issue has been disabled. All new issues should go to
> iss...@sedona.apache.org. Please find the exported issues on GitHub in
> the attached file.
>
> 3. GitHub PRs have been integrated with JIRA. To link a PR to an existing
> JIRA ticket, use [SEDONA-XXX] in the PR title. XXX is the JIRA ticket ID.
> For example, "[SEDONA-1] Move to JTS".
>
> 4. Old code is put in "trunk/import" in case of future IP clearance issues
>
> Thanks,
> Jia
>
>
>

Re: [VOTE] Release Apache Pinot (incubating) 0.5.0 RC2

[Felix Cheung]

+1

Thanks for the update.

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files find (some test .gz are there)
- Source files have ASF headers (except tests & config)

- Did not try compile from source


On Fri, Sep 4, 2020 at 12:06 PM Ting Chen  wrote:

> Hi all,
>
>
>
> This is a call for a vote to release Apache Pinot (incubating) version
>
> 0.5.0.
>
>
>
> Apache Pinot (incubating) is a distributed columnar storage engine that can
>
> ingest data in realtime and serve analytical queries at low latency.
>
>
>
> The Pinot community has voted and approved this release.
>
>
>
> Vote thread:
>
>
> https://lists.apache.org/thread.html/rd12f8915647996cc027299181b0665fd422021bb20cd1a308f467045%40%3Cdev.pinot.apache.org%3E
>
>
>
> Result thread:
>
>
> https://lists.apache.org/thread.html/rd12f8915647996cc027299181b0665fd422021bb20cd1a308f467045%40%3Cdev.pinot.apache.org%3E
>
>
>
> The release candidate:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.5.0-rc2
>
>
>
> Diff with apache-pinot-incubating-0.5.0-rc1
>
> https://github.com/apache/incubator-pinot/commit/d902c1a (Remove the
>
> node_modules codes from the src package)
>
>
>
> Git tag for this release:
>
> https://github.com/apache/incubator-pinot/tree/release-0.5.0-rc2
>
>
>
> Git hash for this release:
>
> d87bbc9032c6efe626eb5f9ef1db4de7aa067179
>
>
>
> The artifacts have been signed with a key: C650A5210408F8F4, which can be
>
> found in the following KEYS file.
>
> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
>
>
>
> Release notes:
>
> https://github.com/apache/incubator-pinot/releases/tag/release-0.5.0-rc2
>
>
>
> Staging repository:
>
> https://repository.apache.org/content/repositories/orgapachepinot-1016
>
>
>
> Documentation on verifying a release candidate:
>
>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
>
>
>
>
> *Special notes for verification: During this step "diff -r
>
> apache-pinot-incubating-${VERSION}-src pinot-git-src", due to Cluster
>
> Manager UI & Query Console UI revamp (#5684), you might see the extra lines
>
> below. It is fine because they are generated code for the revamped
>
> controller UI.*
>
>
>
> *Only in
>
> apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
> dist*
>
> *Only in
>
> apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
>
> package-lock.json*
>
>
>
>
>
> The vote will be open for at least 72 hours or until a necessary number of
>
> votes are reached.
>
>
>
> Please vote accordingly,
>
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
>
>
> Thanks,
>
> Apache Pinot (incubating) team
>
>

Re: [VOTE] Release Apache Pinot (incubating) 0.5.0 RC1 (Please ignore the earlier email sent under non apache Email)

[Felix Cheung]

It’s a bit strange under node_modules.

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- Unexpected binary files

Several strange files are in the source tarball
/pinot-controller/src/main/resources/node_modules/fsevents/build/Release/obj.target/fse/fsevents.o
/pinot-controller/src/main/resources/node_modules/core-util-is/float.patch

about 10 tgz like
/pinot-controller/src/main/resources/node_modules/@webassemblyjs/wasm-parser/webassemblyjs-wasm-parser-1.7.10.tgz

- Source files have ASF headers

Generally, looks like a lot of files under node_modules

- compile from source - didn't build


On Tue, Sep 1, 2020 at 1:43 PM Jialiang Li  wrote:

> +1
>
>
>
> On 2020/09/01 00:54:44, Ting Chen  wrote:
>
> > Hi all,
>
> >
>
> > This is a call for a vote to release Apache Pinot (incubating) version
>
> > 0.5.0.
>
> >
>
> > Apache Pinot (incubating) is a distributed columnar storage engine that
> can
>
> > ingest data in realtime and serve analytical queries at low latency.
>
> >
>
> > The Pinot community has voted and approved this release.
>
> >
>
> > Vote thread:
>
> >
> https://lists.apache.org/thread.html/rd16efae6e7f5f89d0702f3849b1a2e61c1ff25619d62ecf2807a2140%40%3Cdev.pinot.apache.org%3E
>
> >
>
> > Result thread:
>
> >
> https://lists.apache.org/thread.html/rc06b378d62134372ea5091427a0e5002a70a3dd0df630c4c3586a2a4%40%3Cdev.pinot.apache.org%3E
>
> >
>
> > The release candidate:
>
> >
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.5.0-rc1
>
> >
>
> > Git tag for this release:
>
> > https://github.com/apache/incubator-pinot/tree/release-0.5.0-rc1
>
> >
>
> > Git hash for this release:
>
> > 3c40ea207f84a36aa60bc2ff9987431d2d746222
>
> >
>
> > The artifacts have been signed with a key: C650A5210408F8F4, which can be
>
> > found in the following KEYS file.
>
> > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
>
> >
>
> > Release notes:
>
> > https://github.com/apache/incubator-pinot/releases/tag/release-0.5.0-rc1
>
> >
>
> > Staging repository:
>
> > https://repository.apache.org/content/repositories/orgapachepinot-1015
>
> >
>
> > Documentation on verifying a release candidate:
>
> >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
> >
>
> >
>
> > *Special notes for verification: During this step "diff -r
>
> > apache-pinot-incubating-${VERSION}-src pinot-git-src", due to Cluster
>
> > Manager UI & Query Console UI revamp (#5684), you might see the extra
> lines
>
> > below. It is fine because they are generated code for the revamped
>
> > controller UI.*
>
> >
>
> > *Only in
>
> > apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
> dist*
>
> > *Only in
>
> > apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
>
> > node_modules*
>
> > *Only in
>
> > apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
>
> > package-lock.json*
>
> >
>
> >
>
> > The vote will be open for at least 72 hours or until a necessary number
> of
>
> > votes are reached.
>
> >
>
> > Please vote accordingly,
>
> >
>
> > [ ] +1 approve
>
> > [ ] +0 no opinion
>
> > [ ] -1 disapprove with the reason
>
> >
>
> > Thanks,
>
> > Apache Pinot (incubating) team
>
> >
>
>
>
> -
>
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>
>

Re: Podling Crail Report Reminder - September 2020

[Felix Cheung]

Actually I just saw it. Thanks for putting it together.

It is great to hear updates on (hopefully) generating more activities


From: Felix Cheung 
Sent: Tuesday, September 1, 2020 12:35:24 PM
To: dev@crail.apache.org ; 
d...@crail.incubator.apache.org 
Subject: Re: Podling Crail Report Reminder - September 2020

Reminder on report


From: jmcl...@apache.org 
Sent: Saturday, August 29, 2020 6:55:15 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Crail Report Reminder - September 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, 16 September 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/September2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Age Report Reminder - September 2020

[Felix Cheung]

Any volunteers to write this report?


From: jmcl...@apache.org 
Sent: Saturday, August 29, 2020 6:55:20 PM
To: d...@age.incubator.apache.org 
Subject: Podling Age Report Reminder - September 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, 16 September 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/September2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Sedona Report Reminder - September 2020

[Felix Cheung]

Actually I just saw the update from this morning

It’s here
https://github.com/apache/incubator-sedona


On Tue, Sep 1, 2020 at 12:33 PM Felix Cheung  wrote:

> Fantastic. Thank you for all the details. Hopefully the source import will
> be completed soon.
>
>
> On Tue, Sep 1, 2020 at 1:14 AM Jia Yu  wrote:
>
>> Thanks for the comments. I have fixed that.
>>
>>
>>
>> On Mon, Aug 31, 2020 at 10:06 PM Felix Cheung 
>>
>> wrote:
>>
>>
>>
>> > Thank you!
>>
>> >
>>
>> > For last release please change to N/A - I think that is referring to ASF
>>
>> > release.
>>
>> >
>>
>> > Also if you could answer the last three questions in the report too.
>>
>> >
>>
>> >
>>
>> > On Mon, Aug 31, 2020 at 5:43 PM Jia Yu  wrote:
>>
>> >
>>
>> > > Dear Sedona Mentors and other committers,
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > I just added some new content to the Sedona Monthly report:
>>
>> > >
>>
>> > >
>>
>> >
>> https://cwiki.apache.org/confluence/display/INCUBATOR/September2020#sedona
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > Please feel free to edit the report. And, mentors, thank you very much
>>
>> > for
>>
>> > >
>>
>> > > reviewing the report.
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > Regards,
>>
>> > >
>>
>> > > Jia Yu
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > On Sat, Aug 29, 2020 at 6:55 PM  wrote:
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > > 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, 16 September 2020.
>>
>> > >
>>
>> > > > The report for your podling will form a part of the Incubator PMC
>>
>> > >
>>
>> > > > report. The Incubator PMC requires your report to be submitted 2
>> weeks
>>
>> > >
>>
>> > > > before the board meeting, to allow sufficient time for review and
>>
>> > >
>>
>> > > > submission (Wed, September 02).
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Please submit your report with sufficient time to allow the
>> Incubator
>>
>> > >
>>
>> > > > PMC, and subsequently board members to review and digest. Again, the
>>
>> > >
>>
>> > > > very latest you should submit your report is 2 weeks prior to the
>> board
>>
>> > >
>>
>> > > > meeting.
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Candidate names should not be made public before people are actually
>>
>> > >
>>
>> > > > elected, so please do not include the names of potential committers
>> or
>>
>> > >
>>
>> > > > PPMC members in your report.
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Thanks,
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > The Apache Incubator PMC
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Submitting your Report
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > --
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Your report should contain the following:
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > *   Your project name
>>
>> > >
>>
>> > > > *   A brief description of your project, which assumes no knowledge
>> of
>>
>> > >
>>
>> > > > the project or necessarily of its field
>>
>> > >
>>
>> > > > *   A list of the three most important issues to address in the move
>>
>> > >
>>
>> > > > towards graduation.
>>
>> > >
>>
>> > > > *   Any issues that the Incubator PMC or ASF Board might wish/need
>> to
>>
>> > be
>>
>> > >
>>
>> > > > aware of
>>
>> > >
>>
>> > > > *   How has the community developed since the last report
>>
>> > >
>>
>> > > > *   How has the project developed since the last report.
>>
>> > >
>>
>> > > > *   How does the podling rate their own maturity.
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > This should be appended to the Incubator Wiki page at:
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > https://cwiki.apache.org/confluence/display/INCUBATOR/September2020
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Note: This is manually populated. You may need to wait a little
>> before
>>
>> > >
>>
>> > > > this page is created from a template.
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Note: The format of the report has changed to use markdown.
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Mentors
>>
>> > >
>>
>> > > > ---
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Mentors should review reports for their project(s) and sign them
>> off on
>>
>> > >
>>
>> > > > the Incubator wiki page. Signing off reports shows that you are
>>
>> > >
>>
>> > > > following the project - projects that are not signed may raise
>> alarms
>>
>> > >
>>
>> > > > for the Incubator PMC.
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > > > Incubator PMC
>>
>> > >
>>
>> > > >
>>
>> > >
>>
>> > >
>>
>> >
>>
>>
>
>

Re: Podling Crail Report Reminder - September 2020

[Felix Cheung]

Reminder on report


From: jmcl...@apache.org 
Sent: Saturday, August 29, 2020 6:55:15 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Crail Report Reminder - September 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, 16 September 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/September2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Sedona Report Reminder - September 2020

[Felix Cheung]

Fantastic. Thank you for all the details. Hopefully the source import will
be completed soon.


On Tue, Sep 1, 2020 at 1:14 AM Jia Yu  wrote:

> Thanks for the comments. I have fixed that.
>
>
>
> On Mon, Aug 31, 2020 at 10:06 PM Felix Cheung 
>
> wrote:
>
>
>
> > Thank you!
>
> >
>
> > For last release please change to N/A - I think that is referring to ASF
>
> > release.
>
> >
>
> > Also if you could answer the last three questions in the report too.
>
> >
>
> >
>
> > On Mon, Aug 31, 2020 at 5:43 PM Jia Yu  wrote:
>
> >
>
> > > Dear Sedona Mentors and other committers,
>
> > >
>
> > >
>
> > >
>
> > > I just added some new content to the Sedona Monthly report:
>
> > >
>
> > >
>
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/September2020#sedona
>
> > >
>
> > >
>
> > >
>
> > > Please feel free to edit the report. And, mentors, thank you very much
>
> > for
>
> > >
>
> > > reviewing the report.
>
> > >
>
> > >
>
> > >
>
> > > Regards,
>
> > >
>
> > > Jia Yu
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > > On Sat, Aug 29, 2020 at 6:55 PM  wrote:
>
> > >
>
> > >
>
> > >
>
> > > > 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, 16 September 2020.
>
> > >
>
> > > > The report for your podling will form a part of the Incubator PMC
>
> > >
>
> > > > report. The Incubator PMC requires your report to be submitted 2
> weeks
>
> > >
>
> > > > before the board meeting, to allow sufficient time for review and
>
> > >
>
> > > > submission (Wed, September 02).
>
> > >
>
> > > >
>
> > >
>
> > > > Please submit your report with sufficient time to allow the Incubator
>
> > >
>
> > > > PMC, and subsequently board members to review and digest. Again, the
>
> > >
>
> > > > very latest you should submit your report is 2 weeks prior to the
> board
>
> > >
>
> > > > meeting.
>
> > >
>
> > > >
>
> > >
>
> > > > Candidate names should not be made public before people are actually
>
> > >
>
> > > > elected, so please do not include the names of potential committers
> or
>
> > >
>
> > > > PPMC members in your report.
>
> > >
>
> > > >
>
> > >
>
> > > > Thanks,
>
> > >
>
> > > >
>
> > >
>
> > > > The Apache Incubator PMC
>
> > >
>
> > > >
>
> > >
>
> > > > Submitting your Report
>
> > >
>
> > > >
>
> > >
>
> > > > --
>
> > >
>
> > > >
>
> > >
>
> > > > Your report should contain the following:
>
> > >
>
> > > >
>
> > >
>
> > > > *   Your project name
>
> > >
>
> > > > *   A brief description of your project, which assumes no knowledge
> of
>
> > >
>
> > > > the project or necessarily of its field
>
> > >
>
> > > > *   A list of the three most important issues to address in the move
>
> > >
>
> > > > towards graduation.
>
> > >
>
> > > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
>
> > be
>
> > >
>
> > > > aware of
>
> > >
>
> > > > *   How has the community developed since the last report
>
> > >
>
> > > > *   How has the project developed since the last report.
>
> > >
>
> > > > *   How does the podling rate their own maturity.
>
> > >
>
> > > >
>
> > >
>
> > > > This should be appended to the Incubator Wiki page at:
>
> > >
>
> > > >
>
> > >
>
> > > > https://cwiki.apache.org/confluence/display/INCUBATOR/September2020
>
> > >
>
> > > >
>
> > >
>
> > > > Note: This is manually populated. You may need to wait a little
> before
>
> > >
>
> > > > this page is created from a template.
>
> > >
>
> > > >
>
> > >
>
> > > > Note: The format of the report has changed to use markdown.
>
> > >
>
> > > >
>
> > >
>
> > > > Mentors
>
> > >
>
> > > > ---
>
> > >
>
> > > >
>
> > >
>
> > > > Mentors should review reports for their project(s) and sign them off
> on
>
> > >
>
> > > > the Incubator wiki page. Signing off reports shows that you are
>
> > >
>
> > > > following the project - projects that are not signed may raise alarms
>
> > >
>
> > > > for the Incubator PMC.
>
> > >
>
> > > >
>
> > >
>
> > > > Incubator PMC
>
> > >
>
> > > >
>
> > >
>
> > >
>
> >
>
>

Re: Podling Sedona Report Reminder - September 2020

[Felix Cheung]

Thank you!

For last release please change to N/A - I think that is referring to ASF
release.

Also if you could answer the last three questions in the report too.


On Mon, Aug 31, 2020 at 5:43 PM Jia Yu  wrote:

> Dear Sedona Mentors and other committers,
>
>
>
> I just added some new content to the Sedona Monthly report:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/September2020#sedona
>
>
>
> Please feel free to edit the report. And, mentors, thank you very much for
>
> reviewing the report.
>
>
>
> Regards,
>
> Jia Yu
>
>
>
>
>
> On Sat, Aug 29, 2020 at 6:55 PM  wrote:
>
>
>
> > 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, 16 September 2020.
>
> > The report for your podling will form a part of the Incubator PMC
>
> > report. The Incubator PMC requires your report to be submitted 2 weeks
>
> > before the board meeting, to allow sufficient time for review and
>
> > submission (Wed, September 02).
>
> >
>
> > Please submit your report with sufficient time to allow the Incubator
>
> > PMC, and subsequently board members to review and digest. Again, the
>
> > very latest you should submit your report is 2 weeks prior to the board
>
> > meeting.
>
> >
>
> > Candidate names should not be made public before people are actually
>
> > elected, so please do not include the names of potential committers or
>
> > PPMC members in your report.
>
> >
>
> > Thanks,
>
> >
>
> > The Apache Incubator PMC
>
> >
>
> > Submitting your Report
>
> >
>
> > --
>
> >
>
> > Your report should contain the following:
>
> >
>
> > *   Your project name
>
> > *   A brief description of your project, which assumes no knowledge of
>
> > the project or necessarily of its field
>
> > *   A list of the three most important issues to address in the move
>
> > towards graduation.
>
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>
> > aware of
>
> > *   How has the community developed since the last report
>
> > *   How has the project developed since the last report.
>
> > *   How does the podling rate their own maturity.
>
> >
>
> > This should be appended to the Incubator Wiki page at:
>
> >
>
> > https://cwiki.apache.org/confluence/display/INCUBATOR/September2020
>
> >
>
> > Note: This is manually populated. You may need to wait a little before
>
> > this page is created from a template.
>
> >
>
> > Note: The format of the report has changed to use markdown.
>
> >
>
> > Mentors
>
> > ---
>
> >
>
> > Mentors should review reports for their project(s) and sign them off on
>
> > the Incubator wiki page. Signing off reports shows that you are
>
> > following the project - projects that are not signed may raise alarms
>
> > for the Incubator PMC.
>
> >
>
> > Incubator PMC
>
> >
>
>

Re: [VOTE] Graduate Apache TVM as TLP

[Felix Cheung]

+1 (binding)


On Thu, Aug 27, 2020 at 10:02 AM Tianqi Chen  wrote:

> Dear Incubator:
>
>
>
> Following a heated discussion with great support from our mentors,
>
> committers and community members.
>
> The Apache(incubating) TVM community has formally voted for graduation and
>
> bring the case to the IPMC.
>
>
>
> Please also see the community discussion thread[1] and voting thread[2]:
>
>
>
> This is a formal voting thread about Apache TVM's graduation, please Vote:
>
> [ ] +1 - Recommend graduation of Apache TVM as a TLP
>
> [ ]  0 - I don't feel strongly about it, but don't object
>
> [ ] -1 - Do not recommend graduation of Apache TVM because...
>
>
>
> The VOTE will open for at least 72 hours.
>
>
>
> --
>
> The TVM project has been an Apache incubator project for nearly 1.5 year
>
> now. In the past one and half year, the community grew healthily under the
>
> Apache way. Some highlights include:
>
>
>
> - A successful developer conference that we are continuing to host this
> year
>
> - Great community growth, as of now, the community contains 16 PPMC
>
> members, 31 committers, from a diverse list of organizations. We are
>
> actively growing the list monthly.
>
> - Active contributions: ~ 150 PRs merged each month.
>
>
>
> The community has produced two formal apache releases. While we could also
>
> wait until more releases. We feel that the community is mature enough that
>
> we can push for graduation as it is, and continue to push for high quality
>
> releases concurrently.
>
>
>
> For reference, we also put together a maturity evaluation doc[3] under the
>
> Apache maturity model.
>
>
>
> Some additional note about the resolution below: the current PPMC will be
>
> transitioned to the PMC. We have invited all the mentors in the current
>
> PPMC who like to stay involved.
>
>
>
> -
>
>
>
> Establish the Apache TVM Project
>
>
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
>
> the Foundation and consistent with the Foundation's purpose to establish
>
> a Project Management Committee charged with the creation and maintenance
>
> of open-source software, for distribution at no charge to the public,
>
> related to compilation of machine learning models to run on a wide range of
>
> hardware platforms...
>
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache TVM Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
>
>
> RESOLVED, that the Apache TVM Project be and hereby is responsible for the
>
> creation and maintenance of software related to compilation of machine
>
> learning models to run on a wide range of hardware platforms; and be it
>
> further
>
>
>
> RESOLVED, that the office of "Vice President, Apache TVM" be and
>
> hereby is created, the person holding such office to serve at the
>
> direction of the Board of Directors as the chair of the Apache TVM
>
> Project, and to have primary responsibility for management of the
>
> projects within the scope of responsibility of the Apache TVM
>
> Project; and be it further
>
>
>
> RESOLVED, that the persons listed immediately below be and hereby are
>
> appointed to serve as the initial members of the Apache TVM Project:
>
>
>
>  * Tianqi Chen 
>
>  * Timothy Chen 
>
>  * Zhi Chen 
>
>  * Byung-Gon Chun 
>
>  * Ziheng Jiang 
>
>  * Furkan Kamaci 
>
>  * YiZhi Liu 
>
>  * Masahiro Masuda 
>
>  * Thierry Moreau 
>
>  * Jared Roesch 
>
>  * Henry Saputra 
>
>  * Haichen Shen 
>
>  * Markus Weimer 
>
>  * Eddie Yan 
>
>  * Lianmin Zheng 
>
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
>
> the office of Vice President, Apache TVM, to serve in accordance
>
> with and subject to the direction of the Board of Directors and the
>
> Bylaws of the Foundation until death, resignation, retirement, removal
>
> or disqualification, or until a successor is appointed; and be it
>
> further
>
>
>
> RESOLVED, that the Apache TVM Project be and hereby is tasked with
>
> the migration and rationalization of the Apache Incubator TVM
>
> podling; and be it further
>
>
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>
> TVM  podling encumbered upon the Apache Incubator PMC are hereafter
>
> Discharged.
>
>
>
> - [1]
>
>
> https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev.tvm.apache.org%3E
>
> - [2]
>
>
> https://lists.apache.org/thread.html/rd5b8eefe49af09a2d0913758a5e5737b3fdb9072bc0becf4a2b2c7ee%40%3Cdev.tvm.apache.org%3E
>
> - [3]
>
>
> https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing
>
> <
> https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing
> >
>
>

Re: [VOTE] Release Apache ECharts (incubating) 4.9.0 (release candidate 1)

[Felix Cheung]

+1 binding

- incubating in name
- signature and hash are fine
- tarball (see note)
the file unpacks into the current and not a  subdirectory, is a bit strange
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers
- build from source



On Tue, Aug 25, 2020 at 7:50 PM Sheng Wu  wrote:

> +1 binding
>
>
>
> 1. incubating in name
>
> 2. download link correct
>
> 3. LICENSE, NOTICE and DISCLAIMER exist
>
> 4. ASC checked
>
> 5. sha512 exists.
>
>
>
> Good luck.
>
>
>
> Sheng Wu 吴晟
>
> Twitter, wusheng1108
>
>
>
>
>
> Yi Shen  于2020年8月24日周一 下午5:21写道：
>
>
>
> > Thanks, Dave.
>
> >
>
> > We still need 2 more votes.
>
> >
>
> > Thanks a lot.
>
> >
>
> > On Wed, Aug 19, 2020 at 2:19 AM Dave Fisher  wrote:
>
> >
>
> > > +1 (binding)
>
> > >
>
> > > Incubating in name
>
> > > Verified signature and checksum
>
> > > LICENSE checked
>
> > > NOTICE checked
>
> > > DISCLAIMER checked
>
> > > Rat Check passed
>
> > >
>
> > > Regards,
>
> > > Dave
>
> > >
>
> > > > On Aug 9, 2020, at 8:57 PM, Yi Shen  wrote:
>
> > > >
>
> > > > Dear IPMC
>
> > > >
>
> > > > I am pleased to be calling this vote for the release of Apache
> ECharts
>
> > > > (incubating) 4.9.0 (release candidate 1).
>
> > > >
>
> > > > Apache ECharts community has voted and approved the release.
>
> > > >
>
> > > > Vote thread:
>
> > > >
>
> > >
>
> >
> https://lists.apache.org/thread.html/r67639d86c9b5944b1804fca86939052978df9594b45bc0d6474b9fb6%40%3Cdev.echarts.apache.org%3E
>
> > > >
>
> > > > Results thread:
>
> > > >
>
> > >
>
> >
> https://lists.apache.org/thread.html/rd9b5170f1f1bdda97c502aa4435650f86ec2ce14cd372ed3d548ce24%40%3Cdev.echarts.apache.org%3E
>
> > > >
>
> > > > The release candidate to be voted over is available at:
>
> > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.9.0-rc.1/
>
> > > >
>
> > > > The release candidate is signed with a GPG key available at:
>
> > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> > > >
>
> > > > The Git commit for this release is:
>
> > > >
>
> > >
>
> >
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=90243fc
>
> > > >
>
> > > > The Release Note is available in:
>
> > > >
>
> > >
>
> >
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.9.0-rc.1/RELEASE_NOTE.txt
>
> > > >
>
> > > > Build Guide:
>
> > > >
>
> > >
>
> >
> https://github.com/apache/incubator-echarts/blob/4.9.0-rc.1/README.md#build
>
> > > >
>
> > > > Please vote on releasing this package as:
>
> > > > Apache ECharts (incubating) 4.9.0 (release candidate 1)
>
> > > > by "2020-08-13T05:00:00.000Z".
>
> > > >
>
> > > > [ ] +1 Release this package
>
> > > > [ ] 0 I don't feel strongly about it, but don't object
>
> > > > [ ] -1 Do not release this package because...
>
> > > >
>
> > > > Anyone can participate in testing and voting, not just committers,
>
> > please
>
> > > > feel free to try out the release candidate and provide your votes.
>
> > > >
>
> > > > A checklist for reference:
>
> > > >
>
> > >
>
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> > > >
>
> > > > Thanks
>
> > > >
>
> > > > --
>
> > > > Yi Shen
>
> > > > Apache ECharts(incubating) PPMC
>
> > >
>
> > >
>
> > > -
>
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>
> > > For additional commands, e-mail: general-h...@incubator.apache.org
>
> > >
>
> > >
>
> >
>
> > --
>
> > Yi Shen
>
> > Apache ECharts(incubating) PPMC
>
> >
>
>

Re: Planning for the first Apache incubator release

[Felix Cheung]

Great! I’d recommend consider the WIP disclaimer

https://incubator.apache.org/policy/incubation.html#work_in_progress_disclaimer


From: Furkan KAMACI 
Sent: Saturday, August 22, 2020 8:46:35 AM
To: dev@teaclave.apache.org 
Subject: Re: Planning for the first Apache incubator release

Hi,

Thanks for preparing the release Mingshen! I can certainly help too.

Kind Regards,
Furkan KAMACI

On Sat, Aug 22, 2020 at 6:40 PM Matt Sicker  wrote:

> Looking forward to it! I’ve got a bit of experience managing releases in
> other projects, so I can certainly help validate this.
>
> On Fri, Aug 21, 2020 at 22:32 Mingshen Sun  wrote:
>
> > Hi folks,
> >
> >
> >
> > Since we entered the Apache Incubator, we have made a lot of progress
> [1].
> >
> > The current codebase is becoming stable. I propose to make the first
> Apache
> >
> > incubator release, i.e., the first release (0.1.0) of Teaclave. I plan to
> >
> > work on the logistics of releasing an Apache version in the next week.
> >
> > These includes:
> >
> >   - license checking
> >
> >   - code packaging and signing
> >
> >   - composing release notes
> >
> >
> >
> > Before that, I'd like to ask if there are any building blocks missing or
> >
> > any critical bugs still unsolved for the 0.1.0 release. For new features
> >
> > and enhancements, we can put them to the next release.  Thanks.
> >
> >
> >
> > Best,
> >
> > Mingshen Sun
> >
> >
> >
> > - [1] https://github.com/apache/incubator-teaclave/issues/121
> >
> > --
> Matt Sicker 
>

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.9.0

[Felix Cheung]

I see

jlowe is a binding IPMC vote that can carry forward from dev@ vote.

We just need 1 more binding vote.


On Mon, Aug 17, 2020 at 11:06 PM Felix Cheung 
wrote:

> +1 (binding)
>
> - incubating in name
> - signature and hash fine
> - DISCLAIMER is fine
> - LICENSE and NOTICE are fine
> - No unexpected binary files
> - All source files have ASF headers
>
> - didn't try - compile from source
>
>
> On Mon, Aug 17, 2020 at 9:12 PM Wilfred Spiegelenburg 
> wrote:
>
>> Hello IPMC
>>
>>
>>
>> The Apache YuniKorn community has voted and approved the release Apache
>>
>> YuniKorn (incubating) 0.9.0. We now kindly request the IPMC members review
>>
>> and vote in this release.
>>
>>
>>
>> YuniKorn is a standalone, universal resource scheduler that can support
>>
>> both long-running and batch workloads. The current release provides a
>> fully
>>
>> functional resource scheduler for K8s.
>>
>>
>>
>> YuniKorn community vote thread:
>>
>>
>> https://lists.apache.org/thread.html/rcb63f4de161439e90b47b53388028119c35f8137f78847405f6a2d4d%40%3Cdev.yunikorn.apache.org%3E
>>
>>
>>
>> Vote result thread:
>>
>>
>> https://lists.apache.org/thread.html/ra20372465b758b8f9bb3271ec6b4483774eb07af5df83712e7d5ecf7%40%3Cdev.yunikorn.apache.org%3E
>>
>>
>>
>> Issues included in this release:
>>
>> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799
>>
>>
>>
>> The release candidate:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/
>>
>>
>>
>> This release has been signed with a PGP available here:
>>
>> https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS
>>
>>
>>
>> Git tag for the release:
>>
>>   - https://github.com/apache/incubator-yunikorn-core/tree/v0.9.0
>>
>>   - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.9.0
>>
>>   -
>>
>>
>>
>>
>> https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.9.0
>>
>>   - https://github.com/apache/incubator-yunikorn-web/tree/v0.9.0
>>
>>
>>
>> The vote will be open for at least 72 hours or until the necessary number
>>
>> of votes is reached.
>>
>>
>>
>> Please vote accordingly:
>>
>>
>>
>> [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.9.0
>>
>> [ ] +0
>>
>> [ ] -1 Do not approve (please specify the reason)
>>
>>
>>
>> Thanks,
>>
>> Wilfred Spiegelenburg
>>
>> Apache YuniKorn (Incubating)
>>
>>
>
>

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.9.0

[Felix Cheung]

+1 (binding)

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

- didn't try - compile from source


On Mon, Aug 17, 2020 at 9:12 PM Wilfred Spiegelenburg 
wrote:

> Hello IPMC
>
>
>
> The Apache YuniKorn community has voted and approved the release Apache
>
> YuniKorn (incubating) 0.9.0. We now kindly request the IPMC members review
>
> and vote in this release.
>
>
>
> YuniKorn is a standalone, universal resource scheduler that can support
>
> both long-running and batch workloads. The current release provides a fully
>
> functional resource scheduler for K8s.
>
>
>
> YuniKorn community vote thread:
>
>
> https://lists.apache.org/thread.html/rcb63f4de161439e90b47b53388028119c35f8137f78847405f6a2d4d%40%3Cdev.yunikorn.apache.org%3E
>
>
>
> Vote result thread:
>
>
> https://lists.apache.org/thread.html/ra20372465b758b8f9bb3271ec6b4483774eb07af5df83712e7d5ecf7%40%3Cdev.yunikorn.apache.org%3E
>
>
>
> Issues included in this release:
>
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799
>
>
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/
>
>
>
> This release has been signed with a PGP available here:
>
> https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS
>
>
>
> Git tag for the release:
>
>   - https://github.com/apache/incubator-yunikorn-core/tree/v0.9.0
>
>   - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.9.0
>
>   -
>
>
>
>
> https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.9.0
>
>   - https://github.com/apache/incubator-yunikorn-web/tree/v0.9.0
>
>
>
> The vote will be open for at least 72 hours or until the necessary number
>
> of votes is reached.
>
>
>
> Please vote accordingly:
>
>
>
> [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.9.0
>
> [ ] +0
>
> [ ] -1 Do not approve (please specify the reason)
>
>
>
> Thanks,
>
> Wilfred Spiegelenburg
>
> Apache YuniKorn (Incubating)
>
>

Re: Graduation

[Felix Cheung]

For Graduation readiness - Please consider going through
https://community.apache.org/apache-way/apache-project-maturity-model.html

Here is an example https://unomi.apache.org/community-maturity-model-report.html

It works as a guide not a rule, but good to understand where the project stands



From: Junlin Chen 
Sent: Friday, August 7, 2020 10:08:58 AM
To: d...@superset.incubator.apache.org 
Cc: Maxime Beauchemin 
Subject: Re: Graduation

Community and @mentors,

We've been working on graduation, and going through our status file and
checklist
.
Please chime in and help complete it if you have the information.
Superset website and WIKI are being updated, following the Podling Website
Requirements.

Mentors, there are mentor related items that need to be confirmed, please
help check below.

   - You have subscribed to the pmc and general lists.
   - You have access to the incubator repository
   - You have been tracking project progress.

We also noticed that some of the links on the graduation page
 are broken and would
like to bring it to your attention.

Thanks for your support!

Best,
Junlin

On Thu, Jul 30, 2020 at 4:21 PM Maxime Beauchemin  wrote:

> Community and @mentors!
>
> Junlin and I were talking about pushing the graduation process forward,
> and even though I've done it once before, we could really use some help
> around navigating the process.
>
> The first step is to look at the checklist and identify the gaps, and I
> think there are very few at this time.
>
> Can one of our mentors volunteer to provide guidance?
>
> Volunteers are welcomed as always, we'll also communicate as we break down
> the checklist into tasks.
>
> Thanks,
>
> Max
>

Re: [VOTE] Release Apache Superset (incubating) version 0.37.0

[Felix Cheung]

Moon is now on IPMC.


On Thu, Aug 13, 2020 at 7:26 AM Ville Brofeldt 
wrote:

> Thanks Dave,
>
>
>
> That's great news! I look forward to releasing in 5 hours then!
>
>
>
> Ville
>
>
>
> On Thu, Aug 13, 2020, 16:49 Dave Fisher  wrote:
>
>
>
> > Moon’s vote will become binding in 5 hours when 72 hours will have passed
>
> > since NOTICE was sent to the Board.
>
> >
>
> > Regards,
>
> > Dave
>
> >
>
> > Sent from my iPhone
>
> >
>
> > > On Aug 13, 2020, at 1:32 AM, Ville Brofeldt <
> ville.v.brofe...@gmail.com>
>
> > wrote:
>
> > >
>
> > > Thanks a lot for the vote Moon!
>
> > >
>
> > > I checked the IPMC roster, and it appears that unfortunately your vote
>
> > probably won’t count as a binding IPMC vote:
>
> > http://people.apache.org/phonebook.html?uid=moon . So it seems we still
>
> > only have two binding +1 votes.
>
> > >
>
> > > This is another plea to the IPMC to please cast a vote, as we’re now on
>
> > day 9 of the vote and can’t release until we get one more binding +1
> vote.
>
> > >
>
> > > Ville
>
> > >
>
> > >
>
> > >> Wed, Aug 12, 2020 at 5:50 PM moon soo lee  wrote:
>
> > >>
>
> > >> +1 (I asked to join IPMC, but so far I guess my vote is non-binding)
>
> > >>
>
> > >> I checked
>
> > >>
>
> > >> - Build from source
>
> > >>
>
> > >>
>
> > >>
>
> > >
>
> >
>
>

Re: [VOTE] Release Apache Superset (incubating) version 0.37.0

[Felix Cheung]

One more vote please!


On Mon, Aug 10, 2020 at 10:59 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> We need one more vote please, we're anxious to publish this release!
>
>
>
> On Sat, Aug 8, 2020 at 11:17 AM Felix Cheung 
> wrote:
>
>
>
> > Furkan, can you help?
>
> >
>
> > On Fri, Aug 7, 2020 at 11:54 AM Ville Brofeldt <
> ville.v.brofe...@gmail.com
>
> > >
>
> > wrote:
>
> >
>
> > > Justin and Felix,
>
> > >
>
> > >
>
> > >
>
> > > warm thanks for taking the time to vote! The minimum 72h voting time is
>
> > > now complete, and it would be great to get that last missing vote from
>
> > the
>
> > > IPMC to be able to release this highly anticipated release of Apache
>
> > > Superset (Incubating).
>
> > >
>
> > >
>
> > >
>
> > > Thanks,
>
> > >
>
> > > The Apache Superset (Incubating) Team
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > > > On 4. Aug 2020, at 20.19, Ville Brofeldt  >
>
> > > wrote:
>
> > >
>
> > > >
>
> > >
>
> > > > Hello IPMC,
>
> > >
>
> > > >
>
> > >
>
> > > > The Apache Superset (incubating) community has voted on and approved
> a
>
> > > proposal to
>
> > >
>
> > > > release Apache Superset (incubating) version 0.37.0.
>
> > >
>
> > > > The voting thread can be found here:
>
> > >
>
> >
> https://lists.apache.org/thread.html/r76d4a5f850546aed4f5ba94c5c8f7b3cb901d8842ed32832512e715b%40%3Cdev.superset.apache.org%3E
>
> > >
>
> > > >
>
> > >
>
> > > >
>
> > >
>
> > > > Here are the binding +1 votes from mentors, carrying over from the
>
> > > podling vote:
>
> > >
>
> > > > - Felix
>
> > >
>
> > > >
>
> > >
>
> > > > We now kindly request the Incubator PMC members review and vote on
> this
>
> > >
>
> > > > incubator release.
>
> > >
>
> > > >
>
> > >
>
> > > > Apache Superset (incubating) is a modern, enterprise-ready business
>
> > > intelligence web application
>
> > >
>
> > > >
>
> > >
>
> > > > The release candidate:
>
> > >
>
> > > > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.0rc4/
>
> > >
>
> > > >
>
> > >
>
> > > > Git tag for the release:
>
> > >
>
> > > > https://github.com/apache/incubator-superset/tree/0.37.0rc4
>
> > >
>
> > > >
>
> > >
>
> > > > The Change Log for the release:
>
> > >
>
> > > >
>
> > https://github.com/apache/incubator-superset/blob/0.37.0rc4/CHANGELOG.md
>
> > >
>
> > > >
>
> > >
>
> > > > public keys are available at:
>
> > >
>
> > > >
>
> > >
>
> > > > https://www.apache.org/dist/incubator/superset/KEYS
>
> > >
>
> > > >
>
> > >
>
> > > > The vote will be open for at least 72 hours or until the necessary
>
> > number
>
> > >
>
> > > > of votes are reached.
>
> > >
>
> > > >
>
> > >
>
> > > > Please vote accordingly:
>
> > >
>
> > > >
>
> > >
>
> > > > [ ] +1 approve
>
> > >
>
> > > > [ ] +0 no opinion
>
> > >
>
> > > > [ ] -1 disapprove with the reason
>
> > >
>
> > > >
>
> > >
>
> > > > Thanks,
>
> > >
>
> > > > The Apache Superset (Incubating) Team
>
> > >
>
> > >
>
> > >
>
> > >
>
> >
>
>

Re: [VOTE] Release Apache Superset (incubating) version 0.37.0

[Felix Cheung]

Furkan, can you help?

On Fri, Aug 7, 2020 at 11:54 AM Ville Brofeldt 
wrote:

> Justin and Felix,
>
>
>
> warm thanks for taking the time to vote! The minimum 72h voting time is
> now complete, and it would be great to get that last missing vote from the
> IPMC to be able to release this highly anticipated release of Apache
> Superset (Incubating).
>
>
>
> Thanks,
>
> The Apache Superset (Incubating) Team
>
>
>
>
>
>
>
> > On 4. Aug 2020, at 20.19, Ville Brofeldt 
> wrote:
>
> >
>
> > Hello IPMC,
>
> >
>
> > The Apache Superset (incubating) community has voted on and approved a
> proposal to
>
> > release Apache Superset (incubating) version 0.37.0.
>
> > The voting thread can be found here:
> https://lists.apache.org/thread.html/r76d4a5f850546aed4f5ba94c5c8f7b3cb901d8842ed32832512e715b%40%3Cdev.superset.apache.org%3E
>
> >
>
> >
>
> > Here are the binding +1 votes from mentors, carrying over from the
> podling vote:
>
> > - Felix
>
> >
>
> > We now kindly request the Incubator PMC members review and vote on this
>
> > incubator release.
>
> >
>
> > Apache Superset (incubating) is a modern, enterprise-ready business
> intelligence web application
>
> >
>
> > The release candidate:
>
> > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.0rc4/
>
> >
>
> > Git tag for the release:
>
> > https://github.com/apache/incubator-superset/tree/0.37.0rc4
>
> >
>
> > The Change Log for the release:
>
> > https://github.com/apache/incubator-superset/blob/0.37.0rc4/CHANGELOG.md
>
> >
>
> > public keys are available at:
>
> >
>
> > https://www.apache.org/dist/incubator/superset/KEYS
>
> >
>
> > The vote will be open for at least 72 hours or until the necessary number
>
> > of votes are reached.
>
> >
>
> > Please vote accordingly:
>
> >
>
> > [ ] +1 approve
>
> > [ ] +0 no opinion
>
> > [ ] -1 disapprove with the reason
>
> >
>
> > Thanks,
>
> > The Apache Superset (Incubating) Team
>
>
>
>

Re: Graduation

[Felix Cheung]

I can ack the items below for mentors.
As for status - do you mean the podling status file? It’s in svn 
https://incubator.apache.org/guides/mentor.html#initialize_podling_status_page


From: Maxime Beauchemin 
Sent: Friday, August 7, 2020 3:30:05 PM
To: dev@superset.apache.org 
Cc: d...@superset.incubator.apache.org ; 
Maxime Beauchemin 
Subject: Re: Graduation

Thanks Junlin! FYI I just xposted to gene...@incubator.apache.org about the
links being broken.

@mentors another question is how do we edit our graduation status file, and
can we use a different location like Github Wiki for it?

Max

On Fri, Aug 7, 2020 at 11:22 AM Junlin Chen  wrote:

> Community and @mentors,
>
> We've been working on graduation, and going through our status file and
> checklist
> <
> https://docs.google.com/document/d/1Epi_3O9jSY2cbc3Uwcp4NTPjG38dazDTEw1tDvt7xT4/edit#
> >.
> Please chime in and help complete it if you have the information.
> Superset website and WIKI are being updated, following the Podling Website
> Requirements.
>
> Mentors, there are mentor related items that need to be confirmed, please
> help check below.
>
>- You have subscribed to the pmc and general lists.
>- You have access to the incubator repository
>- You have been tracking project progress.
>
> We also noticed that some of the links on the graduation page
>  are broken and would
> like to bring it to your attention.
>
> Thanks for your support!
>
> Best,
> Junlin
>
> On Thu, Jul 30, 2020 at 4:21 PM Maxime Beauchemin  wrote:
>
> > Community and @mentors!
> >
> > Junlin and I were talking about pushing the graduation process forward,
> > and even though I've done it once before, we could really use some help
> > around navigating the process.
> >
> > The first step is to look at the checklist and identify the gaps, and I
> > think there are very few at this time.
> >
> > Can one of our mentors volunteer to provide guidance?
> >
> > Volunteers are welcomed as always, we'll also communicate as we break
> down
> > the checklist into tasks.
> >
> > Thanks,
> >
> > Max
> >
>

Re: Podling report for Sedona

[Felix Cheung]

Great!

On Thu, Aug 6, 2020 at 9:58 PM Jia Yu  wrote:

> Hi Felix,
>
>
>
> I just added the following sentence to the report: "We have removed all
>
> incompatible 3rd party library dependencies in the old codebase. Now we are
>
> waiting for another committer to submit the CLA and then the code will be
>
> imported to ASF Git repo."
>
>
>
> I have contacted the committer Masha via an individual email several days
>
> ago but am still waiting for her response.
>
>
>
> Thanks,
>
> Jia
>
>
>
> On Thu, Aug 6, 2020 at 7:56 PM Felix Cheung 
> wrote:
>
>
>
> > Ok I will take out the date/placeholder.
>
> >
>
> > Jia - it will be great if you go add your thought in the bootstrapping.
>
> >
>
> >
>
> > On Thu, Aug 6, 2020 at 4:23 PM Justin Mclean 
>
> > wrote:
>
> >
>
> > > HI,
>
> > >
>
> > >
>
> > >
>
> > > > The report is already on the wiki page? I’m still trying to see
>
> > > something is missing.
>
> > >
>
> > >
>
> > >
>
> > > It because I use a script to check and it look at the last release date
>
> > > which you’ve left as "-XX-XX”. I know you’re just starting out but
> a
>
> > > little more detail would be appreciated. for instance, an answer to
> “Have
>
> > > your mentors been helpful and responsive?”
>
> > >
>
> > >
>
> > >
>
> > > Thanks,
>
> > >
>
> > > Justin
>
> >
>
>

Re: Podling report for Sedona

[Felix Cheung]

Ok I will take out the date/placeholder.

Jia - it will be great if you go add your thought in the bootstrapping.


On Thu, Aug 6, 2020 at 4:23 PM Justin Mclean 
wrote:

> HI,
>
>
>
> > The report is already on the wiki page? I’m still trying to see
> something is missing.
>
>
>
> It because I use a script to check and it look at the last release date
> which you’ve left as "-XX-XX”. I know you’re just starting out but a
> little more detail would be appreciated. for instance, an answer to “Have
> your mentors been helpful and responsive?”
>
>
>
> Thanks,
>
> Justin