Hi,

I had a brief look at the release, and huge progress is evident.

RAT had nothing but good things to say about both the src and bin release packages. As we discussed earlier, the .css, .mf, and package- list files should probably be reported as RAT issues since we might assume that there is no IP of significance there.

The signatures check out, with only a mild warning:
gpg: Good signature from "Frank Barnaby (CODE SIGNING KEY) <[EMAIL PROTECTED]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.

This just means that Frank should endeavor to have his key signed by some trusted folks in Apache. This is not an issue for an incubating release, just something to work on.

From my perspective there are no issues. Bear in mind I haven't actually tried to use the bits, but I'll leave that to others who know what they're doing.

Nice job.

Craig

On Dec 20, 2007, at 9:31 AM, Craig L Russell wrote:

Hi Jim,

The link looks out-of-date. Try this one:

http://people.apache.org/~jhurley/river/2.1.1

Craig

On Dec 20, 2007, at 8:05 AM, Jim Hurley wrote:

Updated the release candidates to the latest build.
See:
   <http://people.apache.org/~jhurley/2.1.1/>

You'll find:

   apache-river-2.1.1-incubating-bin.zip{, .asc, .md5, .sha}
   apache-river-2.1.1-incubating-src.zip{, .asc, .md5, .sha}

Please take a look.

thanks -Jim


On Dec 13, 2007, at 12:21 AM, Jim Hurley wrote:
:
I've placed the two (-src, -bin) release candidates in the directory:
<http://people.apache.org/~jhurley/river/2.1.1/>

There's some changes to be made (based on Craig's running of
RAT) -- but those are the latest.

-Jim


Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!


Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to