+1 (binding)
* Verified the signature and checksums
* Verified tag
* Build from source
* Run ozonesecure acceptance test
* Start a cluster using bin package
* Run freon rk command with data verification
* Verified information displayed on Recon UI, for both empty cluster and
cluster with data
* Ve
Hi Xi Chen, sorry for not getting back to this earlier.
The proto changes going out in the patch release are ok this time since
there has not been another major release yet. In general this will not
always be the case which is why backporting proto changes should be
avoided. For example if 1.5.0 w
Hi Sammi,
thanks for checking.
For your question:
Q: Have you pushed the artifacts to the apache Nexus? If so, could you share
the link?
A: Yes, I have pushed the artifacts to apache Nexus, the link is provided in
the email:
- Maven artifacts are staged at:
- https://repository.apache.o
Xi,
Thanks for leading the effort of a new release. Have you pushed the
artifacts to the apache Nexus? If so, could you share the link?
Thanks,
Sammi
On Tue, 6 Aug 2024 at 16:45, mrchenx wrote:
> Dear Ozone Devs,
>We have released 1.4.0 on Jan 19th. Now there are 169 new commits
> already
Thanks Xi Chen.
+1
Validated the following:
1. Build from source code.
2. start om/scm/dn and cluster running well.
3. verified `freon ockrw`.
4. verified om/scm HA transfer.
5. using `aws s3` client (ls/cp e.g.), and s3g running well.
6. verified web ui.
Regards,
Hongbing
> On Aug
