Hi,

as just discussed I hereby cancelt he release and rebuild it with all modules 
as RC2.

Julian

Am 11.02.20, 14:11 schrieb "Christofer Dutz" <[email protected]>:

    -1 (binding) (sorry)
    
    Checked:
    - Downloads using tooling: OK
    - Checksum matches: OK
    - Signature matches: OK
    - Signed by apache email: OK
    - Unpacks: OK
    - Existence of LICENSE, NOTICE, README, RELEASE_NOTES: OK
    - README and RELEASE_NOTES match those staged alongside the source 
distribution: OK
    - Content of LICENSE, NOTICE, README, RELEASE_NOTES: OK 
    - NOTICE file has correct year: OK
    - Build according instructions in README: NOT OK
    
    mvnw file wasn't executable, had to make it executable with "chmod +x 
mvnw". Not a big deal.
    A big deal however was that: logstash, interop and all sandbox modules were 
still in a SNAPSHOT version.
    
    Chris
    
    
    Am 11.02.20, 13:45 schrieb "Julian Feinauer" <[email protected]>:
    
        Hey folks,
        
        its release time again!
        As discussed on multiple occasions, the 0.6 release branch will be a 
„LTS“ release of the „old fashioned“ or „hand written“ drivers.
        The develop will be the 0.7.0 branch and will contain the generated 
drivers.
        Please check the RELEASE_NOTES for all details.
        
        ----
        
        Apache PLC4X 0.6.0 has been staged under [2] and it’s time to vote
        on accepting it for release. All Maven artifacts are available under 
[1].
        Voting will be open for 72hr.
        
        A minimum of 3 binding +1 votes and more binding +1 than binding -1
        are required to pass.
        
        Release tag: release/0.6.0
        Hash for the release tag: b6a8ac0a67df93fd85d07981e187aedee1491da0
        
        Per [3] "Before voting +1 PMC members are required to download
        the signed source code package, compile it as provided, and test
        the resulting executable on their own platform, along with also
        verifying that the package meets the requirements of the ASF policy
        on releases."
        
        You can achieve the above by following [4].
        
        [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM 
items in [4])
        [ ]  -1 reject (explanation required)
        
        
        [1] 
https://repository.apache.org/content/repositories/orgapacheplc4x-1020
        [2] https://dist.apache.org/repos/dist/dev/plc4x/0.6.0/rc1
        [3] https://www.apache.org/dev/release.html#approving-a-release
        [4] 
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
        
    
    

Reply via email to