Hi Ant, Thanks for the clarification, I believe we follow this process for all kind of artifacts. My question was specifically about how to verify the functionality of this plugin by using them, I think the README has some information on that now.
+1 from me, I just checked the LICENSE and the artifact signings as required for this release. On Fri, Apr 24, 2009 at 3:19 PM, ant elder <[email protected]> wrote: > On Fri, Apr 24, 2009 at 10:29 AM, Ramkumar R <[email protected]> > wrote: > > Hi Ant, > > > > May be I am not sure how to verify this plugin, can you please post some > > info on this. Thanks. > > > > Its mainly down to the ASF standards and requirements for release > artifacts, so: > > - Is every seperatley distributable artifact correctly licensed, do > they have the correct LICENSE and NOTICE files? > These do if you look within the jars at > > http://people.apache.org/~antelder/tuscany/maven-zip-plugin-alpha1-RC1/org/apache/tuscany/maven/plugins/maven-zip-plugin/alpha1/<http://people.apache.org/%7Eantelder/tuscany/maven-zip-plugin-alpha1-RC1/org/apache/tuscany/maven/plugins/maven-zip-plugin/alpha1/> > you can see the LICENSE and NOTICE files. > > - are the artifacts signed with a valid key? > These are, you can see the .asc files and if you down load those > artifacts and run something like gpg --verify > maven-zip-plugin-alpha1.jar.asc it should be ok > > Those are the main blocking things for these simple maven plugin > releases, if either of those were incorrect a -1 would be warranted. > Then there's stylistic things, is there a correct svn tag, and in > there a RELEASE_NOTES and README file to give some info about what the > release is for, are they full of typos, if you were so inclined you > could try out using the plugin. None of those things are absolutely > required though especially not for an alpha1 release like this and > even if you found issues you could just point them out for fixing in a > later release. > > ...ant > -- Thanks & Regards, Ramkumar Ramalingam
