Dave,
I think the released artifacts are as follows:
1. Source package (src.tar.gz)
2. Convenience binaries for Maven artifacts (heron-artifacts)
1. These should also be uploaded to a Maven repo
3. Convenience binaries for installation per OS (heron-install)
4. Convenience binary for HeronPy
1. we also upload the convenience binaries to PyPi repo
5. Convenience binary for Helm chart (helm folder)
1. Also published to the apache.jfrog.org Helm repository
Are we over complicating our release process by including all of these?
Should we focus on releasing the source artifact and release un-official
convenience artifacts to the external repos (i.e. Maven, PyPi, Helm,
DockerHub)?
On Fri, Jan 14, 2022 at 1:56 PM Dave Fisher <[email protected]> wrote:
> The directory
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc1/
> contains many other artifacts. Does the PPMC intend to release those as
> well?
>
> If yes then the signatures, checksums, LICENSE and NOTICE must be checked.
>
> > On Jan 10, 2022, at 8:14 PM, Nicholas Nezis <[email protected]>
> wrote:
> >
> > Hello Heron Community,
> >
> > This is a call for a vote to the 1st release candidate for Apache Heron,
> > version 0.20.5-incubating.
> > We request project mentors (binded) as well as all contributors
> (unbinded)
> > and users to review and vote on this incubator release.
> >
> > * The tag to be voted upon: fd30626d70e3cc3284dcc527f9d0883f42ff1157
> > The full list of changes and release notes are available
> > at:
> https://github.com/apache/incubator-heron/releases/tag/0.20.5-incubating-rc1
> >
> > Files can be found in dist.apache.org
> > Source:
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc1/heron-0.20.5-incubating-src.tar.gz
> > SHA-512 checksums:
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc1/heron-0.20.5-incubating-src.tar.gz.sha512
> >
> >
> > Please download the source package, and follow the below steps from
> > the root folder of the heron code base. Note that currently Bazel
> > 4.1.0 is required to build this version and approximate build time is
> > 45 minutes.
> > # check that Bazel and other dependencies are setup correctly
> > ./bazel_configure.py
> >
> >
> > To build an install script for your desired platform (debian, and
> > centos are supported for this release) you may run the following
> > command.
> > for Debian10
> > $ bazel build --config=debian_nostyle scripts/packages:binpkgsfor
> > Ubuntu18.04/Ubuntu20.04
> > $ bazel build --config=ubuntu_nostyle scripts/packages:binpkgs
> > for CentOS7
> > $ bazel build --config=centos_nostyle scripts/packages:binpkgs
> >
> > To execute and install Heron from an install script you can follow the
> > steps below:
> >
> >
> > $ chmod +x heron-install-0.20.5-incubating-{distro}.sh
> > $ ./heron-install-0.20.5-incubating-{distro}.sh --user
> >
> > From here you should find disclaimers and other files in your ~/.heron
> > directory.
> > ls ~/.heron/
> >
> > DISCLAIMER NOTICE conf/ etc/ include/
> > release.yaml
> >
> > LICENSE bin/ dist/ examples/ lib/
> >
> >
> > or refer to the compiling
> > guidehttps://heron.incubator.apache.org/docs/next/compiling-overview/
> > to setup the environment, build and run locally.
> >
> > After Bazel is set up and works correctly, you can use these release
> check
> > scripts as well.
> https://github.com/apache/incubator-heron/blob/master/scripts/release_check/README.md#run-individual-release-checks
> > to verify the build. 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
> >
> > Thank you,
> >
> > The Apache Heron (Incubating) Team
>
>
