Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated with final release steps

...

We're

...

starting

...

to

...

move

...

our

...

builds

...

over

...

to

...

using

...

the

...

Apache

...

Nexus

...

repository

...

(repository.apache.org)

...

for

...

releasing

...

SNAPSHOT

...

and

...

release

...

artifacts.

...

More

...

details

...

on

...

releasing

...

artifacts

...

and

...

using

...

Nexus

...

can

...

be

...

found

...

on

...

the

...

Maven

...

website

...

at

...

-

...

http://maven.apache.org/developers/release/apache-release.html

...

Release Steps for OpenJPA 1.3.x

...

-

...

2.1.x

...

  1. Environment

...

  1. setup

...

  1. for

...

  1. releasing

...

  1. artifacts

...

  1. (same

...

  1. for

...

  1. SNAPSHOTs

...

  1. and

...

  1. releases)

...

  1. -

...

    1. Increase

...

    1. the

...

    1. default

...

    1. Java

...

    1. heap

...

    1. available

...

    1. to

...

    1. Maven

...

    1. (required

...

    1. for

...

    1. Java

...

    1. SE

...

    1. 6)

...

    1. Code Block
      none
      none
      
      export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"
      

...

    1. Use the latest Sun 1.6.0

...

    1. JDK

...

    1. Use

...

    1. Maven

...

    1. 2.2.1

...

    1. or

...

    1. later

...

    1. (2.2.1

...

    1. is

...

    1. required

...

    1. for

...

    1. release

...

    1. signing

...

    1. fixes)

...

    1. Make

...

    1. sure

...

    1. the

...

    1. Release Setup steps have been performed.
  1. Prepare the source for release:
    1. Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly. Also, transition any Resolved issues to the Closed state.
    2. Update the text files in a working copy of the openjpa-project subdir -
      1. Update the CHANGES.txt based on the Text release reports from JIRA.
      2. Update the RELEASE-NOTES.html based on the HTML release reports from JIRA.
      3. Review and update README.txt and BUILDING.txt if needed.
      4. Commit any changes back to svn -
        Code Block
        none
        none
        
        $ svn commit -m "updating files for release"
        

...

    1. Stage any Roadmap or Release landing pages on the wiki.
    2. Use "mvn apache-rat:check"

...

    1. to

...

    1. verify

...

    1. the

...

    1. source

...

    1. has

...

    1. the

...

    1. required

...

    1. headers

...

    1. before

...

    1. trying

...

    1. to

...

    1. release.

...

    1. Perform

...

    1. a

...

    1. full

...

    1. build

...

    1. with

...

    1. tests

...

    1. Code Block
      none
      none
      
      $ mvn clean install -Papache-release,docbook-profile,test-derby,bval
      

...

    1. Run the JPA 1.0

...

    1. and

...

    1. JPA

...

    1. 2.0

...

    1. TCKs

...

    1. to

...

    1. verify

...

    1. the

...

    1. latest

...

    1. code

...

    1. passes.

...

    1. Perform a full build and deploy the SNAPSHOT artifacts
      Code Block
      none
      none
      
      $ mvn clean deploy site site-deploy -Papache-release,docbook-profile,test-derby,bval -DskipTests
      

...

    1. Inspect the files in your local target directories to ensure:
      1. All jars and zips include: LICENSE and NOTICE files
      2. The NOTICE files cover all third-party included files (like XSD schemas)
      3. The LICENSE files include any third-party licenses (like XSD schemas)
      4. The openjpa and openjpa-all jars include the right packages.
      5. The openjpa source and release distribution files have the right content.
      6. All jars/zips/poms have .asc (PGP signature) and md5 files
  1. For new major releases (like 2.0.0 to 2.1.0)
    1. Create a sub-branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more disruptive advances in the trunk from potentially causing problems with the release. It also provides a future maintenance branch (like 2.0.x.)

...

    1. A

...

    1. branch

...

    1. can

...

    1. be

...

    1. made

...

    1. by

...

    1. running:

...


    1. Code Block
      none
      none
      
      $ mvn release:branch -DbranchName=2.0.x
      

...

  1. Checkout a clean copy of the trunk/branch

...

  1. to

...

  1. release

...

  1. using

...

  1. command

...

  1. line

...

  1. svn.

...

    1. Do

...

    1. not

...

    1. use

...

    1. Eclipse

...

    1. to

...

    1. do

...

    1. the

...

    1. checkout.

...

    1. The

...

    1. extra

...

    1. dot

...

    1. (.)

...

    1. files

...

    1. created

...

    1. by

...

    1. Eclipse

...

    1. throws

...

    1. off

...

    1. the

...

    1. rat:check

...

    1. processing

...

    1. and

...

    1. will

...

    1. get

...

    1. included

...

    1. in

...

    1. the

...

    1. source

...

    1. distribution.

...


    1. Code Block
      none
      none
      
      $ svn checkout https://svn.apache.org/repos/asf/openjpa/2.0.x/ 2.0.1-rc1/
      

...

  1. (Optional)

...

  1. Do

...

  1. a

...

  1. dry

...

  1. run

...

  1. of

...

  1. the

...

  1. release:prepare

...

  1. step.

...

    1. The

...

    1. dry

...

    1. run

...

    1. will

...

    1. not

...

    1. commit

...

    1. any

...

    1. changes

...

    1. back

...

    1. to

...

    1. SVN

...

    1. and

...

    1. gives

...

    1. you

...

    1. the

...

    1. opportunity

...

    1. to

...

    1. verify

...

    1. that

...

    1. the

...

    1. release

...

    1. process

...

    1. will

...

    1. complete

...

    1. as

...

    1. expected.

...

    1. You

...

    1. will

...

    1. be

...

    1. prompted

...

    1. for

...

    1. the

...

    1. following

...

    1. information

...

    1. :

...

      1. Release

...

      1. version

...

      1. -

...

      1. take

...

      1. the

...

      1. default

...

      1. -

...

      1. (default

...

      1. 2.0.1)

...

      1. SCM

...

      1. release

...

      1. tag

...

      1. -

...

      1. *DO

...

      1. NOT

...

      1. TAKE

...

      1. THE

...

      1. DEFAULT

...

      1. -

...

      1. (default

...

      1. openjpa-parent-2.0.1):

...

      1. :

...

      1. 2.0.1

...

      1. New

...

      1. development

...

      1. version

...

      1. -

...

      1. take

...

      1. the

...

      1. default

...

      1. -

...

      1. (default

...

      1. 2.0.2-SNAPSHOT)

...

      1. optional if you have not specified a GPG passphrase in settings.xml

...

      1. you

...

      1. will

...

      1. be

...

      1. prompted

...

      1. for

...

      1. it.

...

      1. Code Block
        none
        none
        
        $ mvn -Papache-release release:prepare -DdryRun=true
        

...

      1. Note

        If you cancel a release:prepare

...

      1. before

...

      1. it

...

      1. updates

...

      1. the

...

      1. pom.xml

...

      1. versions,

...

      1. then

...

      1. use

...

      1. the

...

      1. release:clean

...

      1. goal

...

      1. to

...

      1. just

...

      1. remove

...

      1. the

...

      1. extra

...

      1. files

...

      1. that

...

      1. were

...

      1. created.

...

    1. Verify that the release process completed as expected
      1. The release plugin will create pom.xml.tag

...

      1. files

...

      1. which

...

      1. contain

...

      1. the

...

      1. changes

...

      1. that

...

      1. would

...

      1. have

...

      1. been

...

      1. committed

...

      1. to

...

      1. SVN.

...

      1. The

...

      1. only

...

      1. differences

...

      1. between

...

      1. pom.xml.tag

...

      1. and

...

      1. it's

...

      1. corresponding

...

      1. pom.xml

...

      1. file

...

      1. should

...

      1. be

...

      1. the

...

      1. version

...

      1. number.

...

      1. If

...

      1. other

...

      1. formatting

...

      1. changes

...

      1. have

...

      1. been

...

      1. made

...

      1. you

...

      1. should

...

      1. review

...

      1. the

...

      1. changes

...

      1. and

...

      1. then

...

      1. commit

...

      1. them

...

      1. -

...

      1. Code Block
        none
        none
        
        $ svn commit -m "fixing formatting for release"
        

...

      1. Assuming the .tag

...

      1. files

...

      1. look

...

      1. OK

...

      1. you

...

      1. may

...

      1. proceed

...

      1. and

...

      1. do

...

      1. any

...

      1. other

...

      1. validation

...

      1. you

...

      1. feel

...

      1. necessary.

...

      1. The

...

      1. following

...

      1. list

...

      1. may

...

      1. be

...

      1. helpful

...

        1. Check

...

        1. release.properties

...

        1. and

...

        1. make

...

        1. sure

...

        1. that

...

        1. the

...

        1. scm

...

        1. properties

...

        1. have

...

        1. the

...

        1. right

...

        1. version.

...

        1. Sometimes

...

        1. the

...

        1. scm

...

        1. location

...

        1. can

...

        1. be

...

        1. the

...

        1. previous

...

        1. version

...

        1. not

...

        1. the

...

        1. next

...

        1. version.

...

        1. verify

...

        1. signatures

...

        1. #Verifying

...

        1. release

...

        1. signatures

...

    1. Once

...

    1. any

...

    1. failures

...

    1. or

...

    1. required

...

    1. updates

...

    1. have

...

    1. been

...

    1. committed

...

    1. to

...

    1. svn,

...

    1. rollback

...

    1. the

...

    1. release

...

    1. prepare

...

    1. files

...

    1. -

...

    1. Code Block
      none
      none
      
      $ mvn -Papache-release release:rollback
      

...

  1. Prepare the release
    1. Run the "release:prepare"

...

    1. step

...

    1. for

...

    1. real

...

    1. this

...

    1. time.

...

    1. You'll

...

    1. be

...

    1. prompted

...

    1. for

...

    1. the

...

    1. same

...

    1. version

...

    1. information

...

    1. and

...

    1. optionally

...

    1. your

...

    1. GPG

...

    1. passphrase

...

    1. again.

...

    1. Note

...

    1. Different

...

    1. arguments

...

    1. and

...

    1. steps

...

    1. are

...

    1. required

...

    1. as

...

    1. there

...

    1. are

...

    1. problems

...

    1. with

...

    1. the

...

    1. maven-jar-plugin

...

    1. and

...

    1. maven-release-plugin

...

    1. when

...

    1. using

...

    1. the

...

    1. test-jar

...

    1. goal.

...

    1. See

...

    1. http://jira.codehaus.org/browse/MJAR-68

...

    1. and

...

    1. http://jira.codehaus.org/browse/MRELEASE-285

...

    1. .

      Code Block
      none
      none
      
      $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests -DpreparationGoals="clean install"
      

...

  1. Backup (zip

...

  1. or

...

  1. tar)

...

  1. your

...

  1. local

...

  1. release

...

  1. candidate

...

  1. directory

...

  1. in

...

  1. case

...

  1. you

...

  1. need

...

  1. to

...

  1. rollback

...

  1. the

...

  1. release

...

  1. after

...

  1. the

...

  1. next

...

  1. step

...

  1. is

...

  1. performed.

...

  1. Code Block
    none
    none
    
    cd ..
    tar -czf 2.0.1-rc1-preRelease.tar.gz 2.0.1-rc1/
    cd 2.0.1-rc1
    

...

  1. Perform the release
    1. This step will create a maven staging repository and site for use in testing and voting. You will be prompted for your repository.apache.org

...

    1. and

...

    1. people.apache.org

...

    1. password

...

    1. several

...

    1. times

...

    1. if

...

    1. you

...

    1. have

...

    1. not

...

    1. added

...

    1. server

...

    1. profiles

...

    1. to

...

    1. your

...

    1. settings.xml.

...

    1. See

...

    1. Release

...

    1. Setup

...

    1. for

...

    1. more

...

    1. information.

...

    1. Code Block
      none
      none
      
      $ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
      

...

    1. Note

      If your local OS userid doesn't

...

    1. match

...

    1. your

...

    1. Apache

...

    1. userid,

...

    1. then

...

    1. you'll

...

    1. have

...

    1. to

...

    1. also

...

    1. override

...

    1. the

...

    1. value

...

    1. provided

...

    1. by

...

    1. the

...

    1. OS

...

    1. to

...

    1. Maven

...

    1. for

...

    1. the

...

    1. site-deploy

...

    1. step

...

    1. to

...

    1. work.

...

    1. This

...

    1. is

...

    1. known

...

    1. to

...

    1. work

...

    1. for

...

    1. Linux,

...

    1. but

...

    1. not

...

    1. for

...

    1. Mac

...

    1. and

...

    1. unknown

...

    1. for

...

    1. Windows.

...

    1. The maven-release-plugin

...

    1. is

...

    1. configured

...

    1. with

...

    1. goals

...

    1. "deploy

...

    1. site

...

    1. site-deploy"

...

    1. and

...

    1. will

...

    1. deploy

...

    1. the

...

    1. site

...

    1. files

...

    1. to

...

    1. a

...

    1. staging-site

...

    1. directory

...

    1. on

...

    1. people.apache.org.

...

  1. Verify

...

  1. the

...

  1. release

...

  1. artifacts

...

    1. Verify

...

    1. the

...

    1. HTML

...

    1. links

...

    1. in

...

    1. staging-site/index.html

...

    1. are

...

    1. correct

...

      1. Update

...

      1. downloads/

...

      1. to

...

      1. apache-openjpa/downloads/

...

      1. Update

...

      1. docs/index.html

...

      1. to

...

      1. apache-openjpa/docs/index.html

...

    1. Verify the staged artifacts in the nexus repo
      1. https://repository.apache.org/index.html

...

      1. Image Added
      2. Enterprise

...

      1. -->

...

      1. Staging

...

      1. Staging

...

      1. tab

...

      1. -->

...

      1. Name

...

      1. column

...

      1. -->

...

      1. org.apache.openjpa

...

      1. Navigate

...

      1. through

...

      1. the

...

      1. artifact

...

      1. tree

...

      1. and

...

      1. make

...

      1. sure

...

      1. that

...

      1. all

...

      1. javadoc,

...

      1. sources,

...

      1. tests,

...

      1. jars,

...

      1. ...

...

      1. have

...

      1. .asc

...

      1. (GPG

...

      1. signature)

...

      1. and

...

      1. .md5

...

      1. files.

...

      1. See

...

      1. http://people.apache.org/~henkp/repo/faq.html

...

      1. and

...

      1. http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig

...

    1. Close

...

    1. the

...

    1. nexus

...

    1. staging

...

    1. repo

...

      1. https://repository.apache.org/index.html

...

      1. Image Added
      2. Enterprise

...

      1. -->

...

      1. Staging

...

      1. Staging

...

      1. tab

...

      1. -->

...

      1. Name

...

      1. column

...

      1. -->

...

      1. org.apache.openjpa

...

      1. Right

...

      1. click

...

      1. on

...

      1. the

...

      1. open

...

      1. staging

...

      1. repo

...

      1. (org.apache.openjpa-XXX)

...

      1. and

...

      1. select

...

      1. Close.

...

  1. Put

...

  1. the

...

  1. release

...

  1. candidate

...

  1. up

...

  1. for

...

  1. a

...

  1. vote

...

    1. Create

...

    1. a

...

    1. VOTE

...

    1. email

...

    1. thread

...

    1. on

...

    1. dev@openjpa

...

    1. to

...

    1. record

...

    1. votes

...

    1. as

...

    1. replies,

...

    1. like

...

    1. -

...

    1. Code Block
      none
      none
      
      To: dev@
      Subject: [VOTE] Apache OpenJPA 2.0.1 Release Candidate
      
      I've created a 2.0.1 release candidate, with the following artifacts up for a vote:
      
      SVN source tag (rXXXXXX):
      https://svn.apache.org/repos/asf/openjpa/tags/2.0.1/
      
      Maven staging repo:
      https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/
      
      Source release:
      https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/org/apache/openjpa/openjpa-parent/2.0.1/openjpa-parent-2.0.1-source-release.zip
      
      Javadoc staging site:
      http://people.apache.org/~dwoods/openjpa/2.0.1/staging-site/apidocs/
      
      PGP release keys (signed using D018E6B1):
      https://svn.apache.org/repos/asf/openjpa/KEYS
      
      
      Vote will be open for 72 hours.
      
      [ ] +1  approve
      [ ] +0  no opinion
      [ ] -1  disapprove (and reason why)
      
      

...

    1. Create a DISCUSS email thread on dev@ for any vote questions, like -
      Code Block
      none
      none
      
      To: dev@
      Subject: [DISCUSS] Apache OpenJPA 2.0.1 Release Candidate
      
      Discussion thread for vote on 2.0.1 release candidate, with SVN source tag (rXXXXXX).
      
      For more information on the release process, checkout -
      http://www.apache.org/dev/release.html
      http://incubator.apache.org/guides/releasemanagement.html
      
      Some of the things to check before voting are:
      - does "mvn apache-rat:check" pass on the source
      - can you build the contents of source-release.zip and svn tag
      - do all of the staged jars/zips contain the required LICENSE and NOTICE files
      - are all of the staged jars signed and the signature verifiable
      - is the signing key in the project's KEYS file and on a public server
      - does the release pass the TCK
      
      

...

    1. Perform a review of the release and cast your vote. See the following for more details on Apache releases -
      1. http://www.apache.org/dev/release.html

...

      1. http://incubator.apache.org/guides/releasemanagement.html

...

    1. A

...

    1. -1

...

    1. vote

...

    1. does

...

    1. not

...

    1. necessarily

...

    1. mean

...

    1. that

...

    1. the

...

    1. vote

...

    1. must

...

    1. be

...

    1. redone,

...

    1. however

...

    1. it

...

    1. is

...

    1. usually

...

    1. a

...

    1. good

...

    1. idea

...

    1. to

...

    1. rollback

...

    1. the

...

    1. release

...

    1. if

...

    1. a

...

    1. -1

...

    1. vote

...

    1. is

...

    1. received.

...

    1. See

...

    1. -

...

    1. #Recovering

...

    1. from

...

    1. a

...

    1. vetoed

...

    1. release

...

    1. After

...

    1. the

...

    1. vote

...

    1. has

...

    1. been

...

    1. open

...

    1. for

...

    1. at

...

    1. least

...

    1. 72

...

    1. hours,

...

    1. has

...

    1. at

...

    1. least

...

    1. three

...

    1. +1

...

    1. PMC

...

    1. votes

...

    1. and

...

    1. no

...

    1. -1

...

    1. votes,

...

    1. then

...

    1. post

...

    1. the

...

    1. results

...

    1. to

...

    1. the

...

    1. vote

...

    1. thread

...

    1. by

...

    1. -

...

      1. reply

...

      1. to

...

      1. the

...

      1. initial

...

      1. email

...

      1. and

...

      1. prepend

...

      1. to

...

      1. the

...

      1. original

...

      1. subject

...

      1. -

...

      1. Code Block
        none
        none
        [RESULTS]

...

      1. Include a list of everyone who voted +1,

...

      1. 0

...

      1. or

...

      1. -1.

...

  1. Finalizing

...

  1. a

...

  1. release

...

    1. Promote

...

    1. the

...

    1. staged

...

    1. nexus

...

    1. artifacts

...

    1. -

...

      1. https://repository.apache.org/index.html

...

      1. Image Added
      2. Enterprise

...

      1. -->

...

      1. Staging

...

      1. Staging

...

      1. tab

...

      1. -->

...

      1. Name

...

      1. column

...

      1. -->

...

      1. org.apache.openjpa

...

      1. Right

...

      1. click

...

      1. on

...

      1. the

...

      1. closed

...

      1. staging

...

      1. repo

...

      1. (org.apache.openjpa-XXX)

...

      1. and

...

      1. select

...

      1. Promote.

...

    1. Copy

...

    1. the

...

    1. staged

...

    1. site

...

    1. over

...

    1. to the openjpa/builds location on people.apache.org.
      1. ssh to people.apache.org
        Code Block
        none
        none
        
        $ mkdir /www/openjpa.apache.org/builds/2.0.1
        $ cp -r ~/public_html/openjpa/2.0.1/staging-site/* /www/openjpa.apache.org/builds/2.0.1/
        $ chmod -R g+w /www/openjpa.apache.org/builds/2.0.1
        
      2. Update the assemblies in the Downloads directory.
        For this, we'll just wget copies of the released assemblies with their signatures and hashes from the Apache repo:
        Code Block
        none
        none
        
        $ cd /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads
        wget https://repository.apache.org/content/repositories/releases/org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-source.zip
        wget https://repository.apache.org/content/repositories/releases/org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-binary.zip
        
        Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP files above.
      3. verify that /www/openjpa.apache.org/builds/2.0.1/docs/manual is populated correctly by comparing it to a previous release.
        Code Block
        none
        none
        
        $ rm /www/openjpa.apache.org/docs/latest
        $ ln -fvs ../builds/2.0.1/apache-openjpa/docs/ /www/openjpa.apache.org/docs/latest 
        
    2. Copy the distribution artifacts over to the distribution area.
      Code Block
      none
      none
      
      mkdir /www/www.apache.org/dist/openjpa/2.0.1
      cp /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads/* /www/www.apache.org/dist/openjpa/2.0.1/
      chgrp -R openjpa /www/www.apache.org/dist/openjpa/2.0.1
      chmod -R g+w /www/www.apache.org/dist/openjpa/2.0.1
      
      1. Optional: Remove the previous version from /dist. Ie if you're publishing 2.0.1 you would remove 2.0.0.
        Code Block
        none
        none
        
        $ rm -rf /www/openjpa.apache.org/dist/openjpa/2.0.1
        
    3. Update the Downloads and Documentation pages with the new release
    4. Update the JIRA versions page to mark the version as "released", and set the date to the date that the release was approved. You may also need to make a new release entry for the next release.
  1. Announcing the release
    1. After the Maven mirrors have had time to update (24 hours to be on the safe side) update the wiki with pointers to the new release
    2. Make a news announcement on the OpenJPA wiki.
    3. Make an announcement about the release on the dev@, user@ and announce@apache.org list as per the Apache Announcement Mailing Lists page)


Recovering from a vetoed release

  1. Reply to the initial vote email and prepend to the original subject -
    Code Block
    none
    none
    [CANCELED]
  2. Rollback the version upgrades in trunk by either -
    1. Restore the 2.0.1-rc1.tar.gz

...

    1. and

...

    1. run

...

    1. Code Block
      none
      none
      
      $ mvn -Papache-release release:

...

    1. rollback
      
    2. Manually revert the versions in trunk to the prior version and commit
  1. Delete the svn tag created by the release:perform step -
    Code Block
    none
    none
    
    $ svn del https://svn.apache.org/repos/asf/openjpa/tags/2.0.1 -m "rollback release attempt"
    

...

  1. Drop the nexus staging repo
    1. https://repository.apache.org/index.html

...

    1. Image Added
    2. Enterprise

...

    1. -->

...

    1. Staging

...

    1. Staging

...

    1. tab

...

    1. -->

...

    1. Name

...

    1. column

...

    1. -->

...

    1. org.apache.openjpa

...

    1. Right

...

    1. click

...

    1. on

...

    1. the

...

    1. closed

...

    1. staging

...

    1. repo

...

    1. (org.apache.openjpa-XXX)

...

    1. and

...

    1. select

...

    1. Drop.

...

  1. Remove

...

  1. the

...

  1. staged

...

  1. site

...

  1. Code Block
    none
    none
    
    $ ssh ${user.name}@people.apache.org 
    $ cd ~/public_html/openjpa
    $ rm -fr ${project.version}
    
  2. Make the required updates that caused the vote to be canceled
  3. Spin another release candidate!


Verifying release signatures

On unix platforms the following command can be executed -

Code Block
none
none
{code}
# Make the required updates that caused the vote to be canceled
# Spin another release candidate!

\\

h3. Verifying release signatures

On unix platforms the following command can be executed -
{code:none}
for file in `find . -type f -iname '*.asc'`
do
    gpg --verify ${file} 
done
{code}

You'll

...

need

...

to

...

look

...

at

...

the

...

output

...

to

...

ensure

...

it

...

contains

...

only

...

good

...

signatures

...

-

Code Block
none
none

{code:none}
gpg: Good signature from ...
gpg: Signature made ...
{code}

\\