Masatake,

Sorry for my late response. I've just started checking the release
artifacts, but the release-3.6.0-RC0 tag doesn't seem to exist in the
GitHub repo yet.
Would you push it so that I can verify the source tarball is created
from the correct source tree?

Kengo Seki <[email protected]>

On Sat, Jul 18, 2026 at 9:07 PM Sebastian Nagel <[email protected]> wrote:
>
> Hi Masatake Iwasaki,
>
> +1 (non-binding)
>
> * packages and documentation look good
> * launched a small cluster on AWS, ARM64, Ubuntu 24.04
> * verified Web UIs, reading/writing to HDFS and S3A (see BIGTOP-4548)
> * successfully run MapReduce and Spark jobs
>
> Thanks a lot for the careful work to push the release candidate! Thanks to 
> all other Bigtop contributors as well!
>
> ~Sebastian
>
> On 2026/07/10 09:04:37 Masatake Iwasaki wrote:
> > This is the vote for release 3.6.0 of Apache Bigtop. (RC0)
> >
> > It fixes the following issues:
> >
> >     
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12356069&styleName=Text&projectId=12311420
> >
> > The vote will be going for at least 72 hours.
> > Please download, test and vote with
> >
> > [ ] +1, accept RC0 as the official 3.6.0 release of Apache Bigtop
> > [ ] +0, I don't care either way,
> > [ ] -1, do not accept RC0 as the official 3.6.0 release of Apache
> > Bigtop, because...
> >
> > Source and binary files:
> >     https://dist.apache.org/repos/dist/dev/bigtop/bigtop-3.6.0-RC0/
> >
> > Maven staging repo:
> >     https://repository.apache.org/content/repositories/orgapachebigtop-1056
> >
> > The git tag to be voted upon is release-3.6.0-RC0:
> >     https://github.com/apache/bigtop/tree/release-3.6.0-RC0
> >
> > Bigtop's KEYS file containing PGP keys we use to sign the release:
> >     https://dist.apache.org/repos/dist/release/bigtop/KEYS
> >
> > The results of packaging, deployment and smoke tests on the CI
> > environment are as follows:
> >     
> > https://cwiki.apache.org/confluence/display/BIGTOP/Overview+of+Bigtop+3.6.0+Support+Matrix
> >
> > Regards,
> > Masatake Iwasaki
> >

Reply via email to