Great work, Jun!

Let's also make some noise for the release on Apache Bigtop blog[1].
Please let me know your username and I'll then grant you the permission.

[1] https://blogs.apache.org/bigtop/


Jun HE <[email protected]> 於 2018年11月21日 週三 下午12:58寫道:

> On behalf of the Apache Bigtop team, I'd love to announce the general
> availability of the Bigtop 1.3.0 release.
>
> The release is available here:
>     https://www.apache.org/dyn/closer.lua/bigtop/bigtop-1.3.0/
>
> A few highlights of this release include:
>
>    - AArch64 architecture is added to the support matrix
>    - updated distributions (centos-7, fedora-26, debian-9, ubuntu-16.04,
>    opensuse-42.3)
>    - new docker images are available for distributions on different
>    architectures
>    - upgraded toolchain to include new tools and latest versions updates
>    - many upgrades to the latest versions of the ecosystem projects
>    (Hadoop, HBase, Hive, Spark, Solr, Flume, Kafka, GPDB and many others)
>    - improved multi-arch support in several components (hadoop, hbase, qfs,
>    ignite-hadoop and etc)
>    - improvements in the deployment for unattended cluster
>    - improvements in the smoke-tests coverage
>
> With Bigtop 1.3.0 the community continues to deliver the most advanced big
> data stack to date. More details about 1.3.0 release are here:
>     http://bigtop.apache.org/release-notes.html
>
> Deploying Bigtop is easy: grab the repo/list file for your favorite Linux
> distribution:
>   https://www.apache.org/dyn/closer.lua/bigtop/bigtop-1.3.0/repos/
> and you'll be running your very own bigdata cluster in no time!
>
> We welcome your help and feedback. For more information on how to report
> problems, and to get involved, visit the project website at:
> http://bigtop.apache.org
>
> I want to emphasize that this is a collaborative work done by project
> contributors and other communities, who continue to devote time to make
> Bigtop a better software. Thank you all for making this release possible!
>
> Thanks,
>
> Jun He (Bigtop 1.3.0 Release Manager)
>

Reply via email to