+1 (binding)

I did find some minor issues though, please see below.
I would really suggest to start maintaining a RELEASE_NOTES file. I usually 
have a look at this in order to see what to expect of the new release.

Chris


[OK] Download all staged artifacts under the url specified in the release vote 
email into a directory we’ll now call download-dir.
[MINOR] Verify the signature is correct: Additional Apache tutorial on how to 
verify downloads can be found here.
        - No trusted Key-chain (might think about going to a key-signing party) 
[OK] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes:
[OK] Unzip the archive:
[MINOR] Verify the existence of DISCLAIMER, LICENSE, NOTICE, README, 
RELEASE_NOTES files in the extracted source bundle.
        - No RELEASE_NOTES
[OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the 
extracted source bundle.
[OK] Run RAT externally (without any exclusions) to ensure there are no 
surprises.
[OK] Search for SNAPSHOT references:
[MINOR] Search for Copyright references, and if they are in headers, make sure 
these files containing them are mentioned in the LICENSE file.
        - Some files listed in LICENSE moved from 
daffodil-test/src/test/resources/org/apache/daffodil/ibm-tests/ to 
daffodil-test-ibm1/src/test/resources/test-suite/ibm-contributed/ without being 
updated in the LICENSE file
                - dpaspc7131.dfdl.xsd
                - dpaspc7132.dfdl.xsd
                - dpaspc7132_2.dfdl.xsd
[OK] Build the project according to the information in the README.md file.




Am 10.07.20, 03:38 schrieb "Beckerle, Mike" <mbecke...@tresys.com>:


    Hoping to get some attention to this.

    We have a user community that requested that we do this point-release with 
a specific fix.
    This is gating their release of a system that uses Daffodil.

    Please review this latest incubator release of Daffodil.

    Thank you

    ________________________________
    From: Mike Beckerle <mbecke...@apache.org>
    Sent: Monday, July 6, 2020 11:45 AM
    To: general@incubator.apache.org <general@incubator.apache.org>
    Subject: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

    The Apache Daffodil community has voted and approved the proposed
    release of Apache Daffodil (incubating) 2.7.0-rc2.

    We now kindly request the Incubator PMC members review and vote on this
    incubator release.

    Daffodil is an open source implementation of the DFDL specification that
    uses DFDL schemas to parse fixed format data into an infoset, which is most
    commonly represented as either XML or JSON. This allows the use of
    well-established XML or JSON technologies and libraries to consume,
    inspect, and manipulate fixed format data in existing solutions. Daffodil
    is also capable of the reverse by serializing or "unparsing" an XML or JSON
    infoset back to the original data format.

    Vote thread:

    
https://mail-archives.apache.org/mod_mbox/daffodil-dev/202007.mbox/%3CEEA6E9860DFB8449AA9F0E561E1B75AAA9709778%40ALPMBAPA07.e2k.ad.ge.com%3E

    Result thread:

    
https://mail-archives.apache.org/mod_mbox/daffodil-dev/202007.mbox/%3CCAM5OWnjr88hP-DVqFh2hKFBMMXepKu39YEt-_E-8Agx2%3DHBOcA%40mail.gmail.com%3E

    All distribution packages, including signatures, digests, etc. can be
    found at:

    https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.7.0-rc2/

    Staging artifacts can be found at:

    https://repository.apache.org/content/repositories/orgapachedaffodil-1018/

    This release has been signed with PGP key 13A680AF, corresponding
    to mbecke...@apache.org, which is included in the KEYS file here:

    https://downloads.apache.org/incubator/daffodil/KEYS

    The release candidate has been tagged in git with v2.7.0-rc2.

    For reference, here is a list of all closed JIRAs tagged with 2.7.0:

    https://s.apache.org/daffodil-issues-2.7.0

    For a summary of the changes in this release, see:

    https://daffodil.apache.org/releases/2.7.0/

    Please review and vote. The vote will be open for at least 72 hours
    (ends on Thursday July 9 at 12 noon US.EDT = UTC-4)

    [ ] +1 approve
    [ ] +0 no opinion
    [ ] -1 disapprove (and reason why)

Reply via email to