As discussed over Github, these issues are not regression and doesn't block 
this release. Based on the release notes, I thought that the validation is done 
for all the arguments while setting cloudmonkey configuration, but it is for 
subset of arguments only. I've reviewed the latest release notes, and it looks 
good. 

I'm changing my vote to +1. Thanks.

Regards,
Suresh

On 30/09/21, 7:02 PM, "Suresh Anaparti" <suresh.anapa...@shapeblue.com> wrote:

    -1

    Tested some API calls with 'cmk.darwin.x86-64'. No issues observed with 
respect to API calls, but noticed some issues (raised in Github) with 
"Validation of arguments while setting cloudmonkey configuration" (mentioned in 
v6.2.0 Release Notes).

    - https://github.com/apache/cloudstack-cloudmonkey/issues/100
    - https://github.com/apache/cloudstack-cloudmonkey/issues/102

    Regards,
    Suresh

    On 24/09/21, 1:14 PM, "Pearl Dsilva" <pearl11...@apache.org> wrote:

        Hi All,

        I've created a v6.2.0 release of CloudMonkey, with the following
        artifacts up for a vote:

        Git Branch and commit SHA:
        
https://github.com/apache/cloudstack-cloudmonkey/commits/8aae61e20c6789133c1d97d49e58f354ba7428c3

        Commit:
        8aae61e20c6789133c1d97d49e58f354ba7428c3

        GitHub pre-release (for RC1 testing, contains changelog,
        artifacts/binaries to test, checksums/usage details):
        https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.2.0

        Source release (checksums and signatures are available at the same 
location):
        https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-6.2.0/

        PGP release keys (signed using 986611B4A5B7090D0145B230E7DB9FC18F16C6AE)
        https://dist.apache.org/repos/dist/release/cloudstack/KEYS

        The vote will be open until October 1st, 2021.

        For sanity in tallying the vote, can PMC members please be sure to
        indicate "(binding)" with their vote?
        [ ] +1 approve
        [ ] +0 no opinion
        [ ] -1 disapprove (and the reason why)

        Regards,
        Pearl Dsilva






 

Reply via email to