Thanks for you notice, Kengo, I forgot to check unittests before release.
I think we can cancel this vote and start a new one after the testcases is 
fixed.

Best Regards,
Zhiguo Wu


---- Replied Message ----
| From | Kengo Seki<[email protected]> |
| Date | 2/24/2023 09:04 |
| To | <[email protected]> |
| Subject | Re: [VOTE] Release Apache Ambari Metrics 2.0.0 RC0 |
Zhiguo, thank you so much for driving this release.
I'm afraid I'm casting 0 for now because I'm not so confident if we
could release it.

I tested checksum and signature:

```
$ svn co https://dist.apache.org/repos/dist/dev/ambari/ambari-metrics-2.0.0-rc0/
$ cd ambari-metrics-2.0.0-rc0
$ diff apache-ambari-metrics-2.0.0-src.tar.gz.sha512 <(sha512sum
apache-ambari-metrics-2.0.0-src.tar.gz)
$ curl -sL https://dist.apache.org/repos/dist/release/ambari/KEYS | gpg --import
$ gpg --verify apache-ambari-metrics-2.0.0-src.tar.gz.asc
apache-ambari-metrics-2.0.0-src.tar.gz
```

Checked files in the source tarball:

```
$ tar xf apache-ambari-metrics-2.0.0-src.tar.gz
$ git clone --depth=1 --branch=release-2.0.0-rc0
https://github.com/apache/ambari-metrics.git /tmp/ambari-metrics
$ diff -r apache-ambari-metrics-2.0.0-src /tmp/ambari-metrics
Only in /tmp/ambari-metrics: .git
Only in /tmp/ambari-metrics: .gitattributes
Only in /tmp/ambari-metrics: .gitignore
```

Made sure it can be successfully built:

```
$ cd apache-ambari-metrics-2.0.0-src
$ mvn clean install -DskipTests

...

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for ambari-metrics 2.0.0-1:
[INFO]
[INFO] ambari-metrics ..................................... SUCCESS [  0.749 s]
[INFO] Ambari Metrics Common .............................. SUCCESS [  3.389 s]
[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  1.539 s]
[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  0.693 s]
[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  0.966 s]
[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  1.874 s]
[INFO] Ambari Metrics Collector ........................... SUCCESS [03:52 min]
[INFO] Ambari Metrics Monitor ............................. SUCCESS [  0.754 s]
[INFO] Ambari Metrics Grafana ............................. SUCCESS [ 13.098 s]
[INFO] Ambari Metrics Host Aggregator ..................... SUCCESS [  6.178 s]
[INFO] Ambari Metrics Assembly ............................ SUCCESS [04:00 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  08:22 min
[INFO] Finished at: 2023-02-24T09:36:41+09:00
[INFO] ------------------------------------------------------------------------
```

So far so good, but I found some unit test failures and filed as
AMBARI-25864, 25865 and 25866.
Some of them seem to be a problem of tests themselves, but I'm not
sure if all of them are so. I need some time to investigate.

Kengo Seki <[email protected]>

On Fri, Feb 24, 2023 at 10:01 AM Jefferson Almeida
<[email protected]> wrote:

+1

Jefferson Almeida

Em qui., 23 de fev. de 2023 às 13:47, Zhiguo Wu <[email protected]>
escreveu:

Hello community,

This is a call for vote to release Apache Ambari Metrics 2.0.0 RC0

The release candidates:
https://dist.apache.org/repos/dist/dev/ambari/ambari-metrics-2.0.0-rc0/

Git tag for the release:
https://github.com/apache/ambari-metrics/tree/release-2.0.0-rc0

Hash for the release tag:
594fe0e73b4308984373aa4e41375d7cdc5a0c20

The artifacts have been signed with Key
D3D5CF25076873C9AA068C0D8F062A5450E25685, which can be found in the KEYS
file:
https://dist.apache.org/repos/dist/release/ambari/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

Best Regards,
Zhiguo Wu


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to