Hi Adam,

The unshaded jars created lots of confusion for the users. People who
directly use the precompiled jars (due to no external internet
connection / no Maven resolvers) should use the shaded jars, rather
than the unshaded jars. A couple of users in the past just put all
shaded/unshaded jars in SPARK_HOME/jars which will break the
environment.

Therefore, I decided to remove all unshaded jars in the released
binary. If someone really wants to use the unshaded jars, they should
use the Maven coordinate together with a Maven dependency resolver. We
will still release those unshaded jars to Maven Central but just not
to ASF release binary.

In addition, ASF's voting process is mainly focused on voting the
source code. Binary is just a convenience release for users, no hard
requirements on it.

Please let me know if this makes sense to you. Or, if you have
suggestions, please also advise.

Thanks,
Jia

On Tue, Oct 10, 2023 at 5:35 AM Adam Binford <adam...@gmail.com> wrote:
>
> In
> https://dist.apache.org/repos/dist/dev/sedona/1.5.0-rc1/apache-sedona-1.5.0-bin.tar.gz
> I only see the shaded artifacts:
>
> % tar -tvf apache-sedona-1.5.0-bin.tar.gz
>
> drwxr-xr-x  0 jiayu  staff       0 Oct  7 17:21 apache-sedona-1.5.0-bin/
>
> -rw-r--r--  0 jiayu  staff 19396408 Oct  7 17:15
> apache-sedona-1.5.0-bin/sedona-spark-shaded-3.0_2.13-1.5.0.jar
>
> -rw-r--r--  0 jiayu  staff 19510994 Oct  7 17:18
> apache-sedona-1.5.0-bin/sedona-spark-shaded-3.4_2.12-1.5.0.jar
>
> -rw-r--r--  0 jiayu  staff 18519327 Oct  7 17:12
> apache-sedona-1.5.0-bin/sedona-flink-shaded_2.12-1.5.0.jar
>
> -rw-r--r--  0 jiayu  staff 19576717 Oct  7 17:12
> apache-sedona-1.5.0-bin/sedona-spark-shaded-3.0_2.12-1.5.0.jar
>
> -rw-r--r--  0 jiayu  staff 19330678 Oct  7 17:21
> apache-sedona-1.5.0-bin/sedona-spark-shaded-3.4_2.13-1.5.0.jar
> I assume all the unshaded artifacts should be in there as well?
>
> On Mon, Oct 9, 2023 at 7:02 AM 若井幸夫 <swa...@apache.org> wrote:
>
> > +1
> >
> > I checked:
> > * Download links are valid
> > * Checksums and PGP signatures are valid
> > * NOTICE is included
> > * Source code artifacts have correct names matching the current release
> > * The project can compile from the source code
> >
> > 2023年10月9日(月) 16:28 Kristin Cowalcijk <kontinuat...@apache.org>:
> >
> > > +1 (voting using my apache.org email again, please consolidate this
> > > with my previous vote as one single vote)
> > >
> > > I checked:
> > > * Download links are valid
> > > * Checksums and PGP signatures are valid
> > > * NOTICE is included
> > > * Source code artifacts have correct names matching the current release
> > > * The project can compile from the source code
> > >
> > > On Sun, Oct 8, 2023 at 6:02 AM Jia Yu <ji...@apache.org> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > This is a call for vote on Apache Sedona 1.5.0-rc1. Please refer to
> > > > the changes listed at the bottom of this email.
> > > >
> > > > Release notes:
> > >
> > https://github.com/apache/sedona/blob/sedona-1.5.0-rc1/docs/setup/release-notes.md
> > > >
> > > > Build instructions:
> > > >
> > >
> > https://github.com/apache/sedona/blob/sedona-1.5.0-rc1/docs/setup/compile.md
> > > >
> > > > GitHub tag:
> > > https://github.com/apache/sedona/releases/tag/sedona-1.5.0-rc1
> > > >
> > > > GPG public key to verify the Release:
> > > https://downloads.apache.org/sedona/KEYS
> > > >
> > > > Source code and binaries:
> > > > https://dist.apache.org/repos/dist/dev/sedona/1.5.0-rc1/
> > > >
> > > > The vote will be open for at least 72 hours or until at least 3 "+1"
> > > > PMC votes are cast
> > > >
> > > > Instruction for checking items on the checklist:
> > > > https://sedona.apache.org/community/vote/
> > > >
> > > > We recommend you use this Jupyter notebook on MyBinder to perform this
> > > > task:
> > >
> > https://mybinder.org/v2/gh/jiayuasu/sedona-tools/HEAD?labpath=binder%2Fverify-release.ipynb
> > > >
> > > > **Please vote accordingly and you must provide your checklist for your
> > > vote**.
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > Checklist:
> > > > [ ] Download links are valid.
> > > > [ ] Checksums and PGP signatures are valid.
> > > > [ ] 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
> > > >
> > > > Thanks,
> > > > Jia
> > >
> >
>
>
> --
> Adam Binford

Reply via email to