You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by sebb <se...@gmail.com> on 2008/01/14 11:58:50 UTC
Re: [Vote] Apache River 2.1.1 Incubating Release
The NOTICE files need to be updated for 2008, i.e. replace 2007 with
2007-2008 on line 3.
The hash files use a format which is difficult to use, as the hashes
may be split over two lines.
The common MD5 format is either
hex{32}
(i.e. no spaces between hex digits)
or
hex{32}<SP>(<SP>|*)filename
Similarly for SHA1.
Also the SHA1 hashes normally have the suffix ".sha1" rather than ".sha"
On 14/01/2008, Jim Hurley <ji...@mac.com> wrote:
> Incubator PMC:
>
> The River community voted on and has approved a proposal to release
> River 2.1.1 incubating. This is the first release from our project.
> We would
> like to request permission of the Incubator PMC to publish the release
> on
> the River Download page.
>
> The vote will be open through Wednesday, January 16th.
>
> Thanks!
>
> -Jim
> jhurley@apache.org
>
>
> Release Proposal:
> <http://people.apache.org/~fbarnaby/river/2.1.1/>
>
> RAT output:
> <http://people.apache.org/~fbarnaby/river/2.1.1/rat_output.txt>
>
> Vote result:
> <http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200801.mbox/%3cD757B3BB-33B4-4984-BE51-624A7C3FCC19@mac.com%3e
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by sebb <se...@gmail.com>.
On 14/01/2008, sebb <se...@gmail.com> wrote:
> On 14/01/2008, Jukka Zitting <ju...@gmail.com> wrote:
> > Hi,
> >
> > On Jan 14, 2008 12:58 PM, sebb <se...@gmail.com> wrote:
> > > The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> > > 2007-2008 on line 3.
> >
> > The release was rolled on Jan 4th and there are no code changes since
> > 2007, so I'd consider this at best a minor issue, probably even better
> > to let the date remain 2007.
>
> Well, the Ant files seem to have been changed in 2008.
>
> > > The hash files use a format which is difficult to use, as the hashes
> > > may be split over two lines.
> >
> > Not a blocker IMHO, but something we may want to change in future releases.
>
> Agreed that it's not a blocker. The files can even be fixed manually if desired.
>
> > I guess the checksums were generated with default Solaris tools. You
> > can use "openssl md5" and "openssl sha1" to generate checksum output
> > in the format Sebastian described.
>
> Well, the format is closer, as the hash is not broken over two lines,
> for example:
>
> MD5(filename)= 464069695e3ac4998898d0633f8df032
>
> > > Also the SHA1 hashes normally have the suffix ".sha1" rather than ".sha"
> >
> > Actually the suffix should be ".sha" and not ".sha1". See the "not
> > normative" policy (a recommendation? :-) described in
> > http://www.apache.org/dev/release-signing.html#policy.
>
> OK, I had not noticed that.
>
The document refers to SHA digests, not SHA-1 digests specifically.
Further investigation shows that these are not the same, at least for openssl:
pwd ~ : openssl sha /dev/null
SHA(/dev/null)= f96cea198ad1dd5617ac084a3d92c6107708c0ef
pwd ~ : openssl sha1 /dev/null
SHA1(/dev/null)= da39a3ee5e6b4b0d3255bfef95601890afd80709
pwd ~ :
[I assume that "openssl sha" means SHA-0, but I could be wrong]
The document does not mention openssl, and gpg does not seem to
support SHA digests (whatever those may be), so presumably SHA means
SHA-1 in the document.
> Clearly a lot of other projects have not noticed either as there are
> 213 sha and 776 sha1 files under /www/www.apache.org/dist/ - so my
> statement was literally correct ;-)
>
> > BR,
> >
> > Jukka Zitting
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by sebb <se...@gmail.com>.
On 14/01/2008, sebb <se...@gmail.com> wrote:
> On 14/01/2008, Jukka Zitting <ju...@gmail.com> wrote:
> > Hi,
> >
> > On Jan 14, 2008 12:58 PM, sebb <se...@gmail.com> wrote:
> > > The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> > > 2007-2008 on line 3.
> >
> > The release was rolled on Jan 4th and there are no code changes since
> > 2007, so I'd consider this at best a minor issue, probably even better
> > to let the date remain 2007.
>
> Well, the Ant files seem to have been changed in 2008.
>
> > > The hash files use a format which is difficult to use, as the hashes
> > > may be split over two lines.
> >
> > Not a blocker IMHO, but something we may want to change in future releases.
>
> Agreed that it's not a blocker. The files can even be fixed manually if desired.
>
> > I guess the checksums were generated with default Solaris tools. You
> > can use "openssl md5" and "openssl sha1" to generate checksum output
> > in the format Sebastian described.
>
> Well, the format is closer, as the hash is not broken over two lines,
> for example:
>
> MD5(filename)= 464069695e3ac4998898d0633f8df032
>
> > > Also the SHA1 hashes normally have the suffix ".sha1" rather than ".sha"
> >
> > Actually the suffix should be ".sha" and not ".sha1". See the "not
> > normative" policy (a recommendation? :-) described in
> > http://www.apache.org/dev/release-signing.html#policy.
>
> OK, I had not noticed that.
>
The document refers to SHA digests, not SHA-1 digests specifically.
Further investigation shows that these are not the same, at least for openssl:
pwd ~ : openssl sha /dev/null
SHA(/dev/null)= f96cea198ad1dd5617ac084a3d92c6107708c0ef
pwd ~ : openssl sha1 /dev/null
SHA1(/dev/null)= da39a3ee5e6b4b0d3255bfef95601890afd80709
pwd ~ :
[I assume that "openssl sha" means SHA-0, but I could be wrong]
The document does not mention openssl, and gpg does not seem to
support SHA digests (whatever those may be), so presumably SHA means
SHA-1 in the document.
> Clearly a lot of other projects have not noticed either as there are
> 213 sha and 776 sha1 files under /www/www.apache.org/dist/ - so my
> statement was literally correct ;-)
>
> > BR,
> >
> > Jukka Zitting
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by Frank Barnaby <Fr...@Sun.COM>.
On Jan 14, 2008, at 06:53, sebb wrote:
> On 14/01/2008, Jukka Zitting <ju...@gmail.com> wrote:
>>
>> I guess the checksums were generated with default Solaris tools. You
>> can use "openssl md5" and "openssl sha1" to generate checksum output
>> in the format Sebastian described.
>
> Well, the format is closer, as the hash is not broken over two lines,
> for example:
>
> MD5(filename)= 464069695e3ac4998898d0633f8df032
The format of the MD5 files for projects at Apache appear to
be inconsistent at best. Out of approximately 57 projects
with a total of 2784 md5 files (probably less since I didn't
think to exclude sym-links) in the dist directory, I've
counted at least 7 different formats:
most common format (1504 md5 files: 54%):
"checksum"
(sum only with no white space)
second most common format (976 md5 files: 35%):
"checksum filename"
third most common format (269 md5 files: 10%):
"MD5 (filename) = checksum"
(with 2 or 3 variations in terms of white space)
And then there are a few other formats that I won't bother
to mention.
The following projects are just a subset of projects which
use the most common format:
ant
avalon
commons
db
excalibur
geronimo
hivemind
jackrabbit
lucene
maven
struts
tomcat
The following projects, among others, use the second most common
format, and you'll notice that some of these also appear in the
above list.
avalon
commons
excalibur
httpd
lucene
maven
struts
tomcat
Consistency is clearly absent with regard to MD5 formats. Apache
Commons, for example, uses three different MD5 formats.
I'm tempted to go with the most common practice, which is to only
use the checksum in the *.md5 files. Comments?
Frank
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by sebb <se...@gmail.com>.
On 14/01/2008, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Jan 14, 2008 12:58 PM, sebb <se...@gmail.com> wrote:
> > The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> > 2007-2008 on line 3.
>
> The release was rolled on Jan 4th and there are no code changes since
> 2007, so I'd consider this at best a minor issue, probably even better
> to let the date remain 2007.
Well, the Ant files seem to have been changed in 2008.
> > The hash files use a format which is difficult to use, as the hashes
> > may be split over two lines.
>
> Not a blocker IMHO, but something we may want to change in future releases.
Agreed that it's not a blocker. The files can even be fixed manually if desired.
> I guess the checksums were generated with default Solaris tools. You
> can use "openssl md5" and "openssl sha1" to generate checksum output
> in the format Sebastian described.
Well, the format is closer, as the hash is not broken over two lines,
for example:
MD5(filename)= 464069695e3ac4998898d0633f8df032
> > Also the SHA1 hashes normally have the suffix ".sha1" rather than ".sha"
>
> Actually the suffix should be ".sha" and not ".sha1". See the "not
> normative" policy (a recommendation? :-) described in
> http://www.apache.org/dev/release-signing.html#policy.
OK, I had not noticed that.
Clearly a lot of other projects have not noticed either as there are
213 sha and 776 sha1 files under /www/www.apache.org/dist/ - so my
statement was literally correct ;-)
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by Frank Barnaby <Fr...@Sun.COM>.
On Jan 14, 2008, at 06:14, Jukka Zitting wrote:
> Hi,
>
> On Jan 14, 2008 12:58 PM, sebb <se...@gmail.com> wrote:
>> The NOTICE files need to be updated for 2008, i.e. replace 2007 with
>> 2007-2008 on line 3.
>
> The release was rolled on Jan 4th and there are no code changes since
> 2007, so I'd consider this at best a minor issue, probably even better
> to let the date remain 2007.
>
>> The hash files use a format which is difficult to use, as the hashes
>> may be split over two lines.
>
> Not a blocker IMHO, but something we may want to change in future
> releases.
GnuPG split the output into two lines because of the length of
prefixed file name. This is trivial to fix.
> I guess the checksums were generated with default Solaris tools. You
> can use "openssl md5" and "openssl sha1" to generate checksum output
> in the format Sebastian described.
I used GnuPG to generate the checksums, an option suggested in
the release signing doc:
http://www.apache.org/dev/release-signing.html#md5
>
>> Also the SHA1 hashes normally have the suffix ".sha1" rather than
>> ".sha"
>
> Actually the suffix should be ".sha" and not ".sha1". See the "not
> normative" policy (a recommendation? :-) described in
> http://www.apache.org/dev/release-signing.html#policy.
The .sha extension is also mentioned in the in the SHA section
of the release signing doc:
http://www.apache.org/dev/release-signing.html#sha-checksum
Frank
>
>
> BR,
>
> Jukka Zitting
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by sebb <se...@gmail.com>.
On 14/01/2008, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Jan 14, 2008 12:58 PM, sebb <se...@gmail.com> wrote:
> > The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> > 2007-2008 on line 3.
>
> The release was rolled on Jan 4th and there are no code changes since
> 2007, so I'd consider this at best a minor issue, probably even better
> to let the date remain 2007.
Well, the Ant files seem to have been changed in 2008.
> > The hash files use a format which is difficult to use, as the hashes
> > may be split over two lines.
>
> Not a blocker IMHO, but something we may want to change in future releases.
Agreed that it's not a blocker. The files can even be fixed manually if desired.
> I guess the checksums were generated with default Solaris tools. You
> can use "openssl md5" and "openssl sha1" to generate checksum output
> in the format Sebastian described.
Well, the format is closer, as the hash is not broken over two lines,
for example:
MD5(filename)= 464069695e3ac4998898d0633f8df032
> > Also the SHA1 hashes normally have the suffix ".sha1" rather than ".sha"
>
> Actually the suffix should be ".sha" and not ".sha1". See the "not
> normative" policy (a recommendation? :-) described in
> http://www.apache.org/dev/release-signing.html#policy.
OK, I had not noticed that.
Clearly a lot of other projects have not noticed either as there are
213 sha and 776 sha1 files under /www/www.apache.org/dist/ - so my
statement was literally correct ;-)
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Jan 14, 2008 12:58 PM, sebb <se...@gmail.com> wrote:
> The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> 2007-2008 on line 3.
The release was rolled on Jan 4th and there are no code changes since
2007, so I'd consider this at best a minor issue, probably even better
to let the date remain 2007.
> The hash files use a format which is difficult to use, as the hashes
> may be split over two lines.
Not a blocker IMHO, but something we may want to change in future releases.
I guess the checksums were generated with default Solaris tools. You
can use "openssl md5" and "openssl sha1" to generate checksum output
in the format Sebastian described.
> Also the SHA1 hashes normally have the suffix ".sha1" rather than ".sha"
Actually the suffix should be ".sha" and not ".sha1". See the "not
normative" policy (a recommendation? :-) described in
http://www.apache.org/dev/release-signing.html#policy.
BR,
Jukka Zitting
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by sebb <se...@gmail.com>.
On 14/01/2008, Craig L Russell <Cr...@sun.com> wrote:
>
> On Jan 14, 2008, at 2:58 AM, sebb wrote:
>
> > The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> > 2007-2008 on line 3.
>
> Not a blocker for me.
> >
> > The hash files use a format which is difficult to use, as the hashes
> > may be split over two lines.
> >
> > The common MD5 format is either
> >
> > hex{32}
> > (i.e. no spaces between hex digits)
> >
> > or
> >
> > hex{32}<SP>(<SP>|*)filename
> >
> > Similarly for SHA1.
> >
> > Also the SHA1 hashes normally have the suffix ".sha1" rather than
> > ".sha"
I was wrong about that - they should be called .sha - see Jukka's reply.
> The easiest way to fix this is to remove the .sha files. If the .md5
> and .asc checksums are good, the sha is just not needed.
>
So the .sha files can be kept.
> Craig
> >
> > On 14/01/2008, Jim Hurley <ji...@mac.com> wrote:
> >> Incubator PMC:
> >>
> >> The River community voted on and has approved a proposal to release
> >> River 2.1.1 incubating. This is the first release from our project.
> >> We would
> >> like to request permission of the Incubator PMC to publish the
> >> release
> >> on
> >> the River Download page.
> >>
> >> The vote will be open through Wednesday, January 16th.
> >>
> >> Thanks!
> >>
> >> -Jim
> >> jhurley@apache.org
> >>
> >>
> >> Release Proposal:
> >> <http://people.apache.org/~fbarnaby/river/2.1.1/>
> >>
> >> RAT output:
> >> <http://people.apache.org/~fbarnaby/river/2.1.1/rat_output.txt>
> >>
> >> Vote result:
> >> <http://mail-archives.apache.org/mod_mbox/incubator-river-dev/
> >> 200801.mbox/%3cD757B3BB-33B4-4984-BE51-624A7C3FCC19@mac.com%3e
> >>>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by sebb <se...@gmail.com>.
On 14/01/2008, Craig L Russell <Cr...@sun.com> wrote:
>
> On Jan 14, 2008, at 2:58 AM, sebb wrote:
>
> > The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> > 2007-2008 on line 3.
>
> Not a blocker for me.
> >
> > The hash files use a format which is difficult to use, as the hashes
> > may be split over two lines.
> >
> > The common MD5 format is either
> >
> > hex{32}
> > (i.e. no spaces between hex digits)
> >
> > or
> >
> > hex{32}<SP>(<SP>|*)filename
> >
> > Similarly for SHA1.
> >
> > Also the SHA1 hashes normally have the suffix ".sha1" rather than
> > ".sha"
I was wrong about that - they should be called .sha - see Jukka's reply.
> The easiest way to fix this is to remove the .sha files. If the .md5
> and .asc checksums are good, the sha is just not needed.
>
So the .sha files can be kept.
> Craig
> >
> > On 14/01/2008, Jim Hurley <ji...@mac.com> wrote:
> >> Incubator PMC:
> >>
> >> The River community voted on and has approved a proposal to release
> >> River 2.1.1 incubating. This is the first release from our project.
> >> We would
> >> like to request permission of the Incubator PMC to publish the
> >> release
> >> on
> >> the River Download page.
> >>
> >> The vote will be open through Wednesday, January 16th.
> >>
> >> Thanks!
> >>
> >> -Jim
> >> jhurley@apache.org
> >>
> >>
> >> Release Proposal:
> >> <http://people.apache.org/~fbarnaby/river/2.1.1/>
> >>
> >> RAT output:
> >> <http://people.apache.org/~fbarnaby/river/2.1.1/rat_output.txt>
> >>
> >> Vote result:
> >> <http://mail-archives.apache.org/mod_mbox/incubator-river-dev/
> >> 200801.mbox/%3cD757B3BB-33B4-4984-BE51-624A7C3FCC19@mac.com%3e
> >>>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
>
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by Craig L Russell <Cr...@Sun.COM>.
On Jan 14, 2008, at 2:58 AM, sebb wrote:
> The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> 2007-2008 on line 3.
Not a blocker for me.
>
> The hash files use a format which is difficult to use, as the hashes
> may be split over two lines.
>
> The common MD5 format is either
>
> hex{32}
> (i.e. no spaces between hex digits)
>
> or
>
> hex{32}<SP>(<SP>|*)filename
>
> Similarly for SHA1.
>
> Also the SHA1 hashes normally have the suffix ".sha1" rather than
> ".sha"
The easiest way to fix this is to remove the .sha files. If the .md5
and .asc checksums are good, the sha is just not needed.
Craig
>
> On 14/01/2008, Jim Hurley <ji...@mac.com> wrote:
>> Incubator PMC:
>>
>> The River community voted on and has approved a proposal to release
>> River 2.1.1 incubating. This is the first release from our project.
>> We would
>> like to request permission of the Incubator PMC to publish the
>> release
>> on
>> the River Download page.
>>
>> The vote will be open through Wednesday, January 16th.
>>
>> Thanks!
>>
>> -Jim
>> jhurley@apache.org
>>
>>
>> Release Proposal:
>> <http://people.apache.org/~fbarnaby/river/2.1.1/>
>>
>> RAT output:
>> <http://people.apache.org/~fbarnaby/river/2.1.1/rat_output.txt>
>>
>> Vote result:
>> <http://mail-archives.apache.org/mod_mbox/incubator-river-dev/
>> 200801.mbox/%3cD757B3BB-33B4-4984-BE51-624A7C3FCC19@mac.com%3e
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by Craig L Russell <Cr...@Sun.COM>.
On Jan 14, 2008, at 2:58 AM, sebb wrote:
> The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> 2007-2008 on line 3.
Not a blocker for me.
>
> The hash files use a format which is difficult to use, as the hashes
> may be split over two lines.
>
> The common MD5 format is either
>
> hex{32}
> (i.e. no spaces between hex digits)
>
> or
>
> hex{32}<SP>(<SP>|*)filename
>
> Similarly for SHA1.
>
> Also the SHA1 hashes normally have the suffix ".sha1" rather than
> ".sha"
The easiest way to fix this is to remove the .sha files. If the .md5
and .asc checksums are good, the sha is just not needed.
Craig
>
> On 14/01/2008, Jim Hurley <ji...@mac.com> wrote:
>> Incubator PMC:
>>
>> The River community voted on and has approved a proposal to release
>> River 2.1.1 incubating. This is the first release from our project.
>> We would
>> like to request permission of the Incubator PMC to publish the
>> release
>> on
>> the River Download page.
>>
>> The vote will be open through Wednesday, January 16th.
>>
>> Thanks!
>>
>> -Jim
>> jhurley@apache.org
>>
>>
>> Release Proposal:
>> <http://people.apache.org/~fbarnaby/river/2.1.1/>
>>
>> RAT output:
>> <http://people.apache.org/~fbarnaby/river/2.1.1/rat_output.txt>
>>
>> Vote result:
>> <http://mail-archives.apache.org/mod_mbox/incubator-river-dev/
>> 200801.mbox/%3cD757B3BB-33B4-4984-BE51-624A7C3FCC19@mac.com%3e
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [Vote] Apache River 2.1.1 Incubating Release
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Jan 14, 2008 12:58 PM, sebb <se...@gmail.com> wrote:
> The NOTICE files need to be updated for 2008, i.e. replace 2007 with
> 2007-2008 on line 3.
The release was rolled on Jan 4th and there are no code changes since
2007, so I'd consider this at best a minor issue, probably even better
to let the date remain 2007.
> The hash files use a format which is difficult to use, as the hashes
> may be split over two lines.
Not a blocker IMHO, but something we may want to change in future releases.
I guess the checksums were generated with default Solaris tools. You
can use "openssl md5" and "openssl sha1" to generate checksum output
in the format Sebastian described.
> Also the SHA1 hashes normally have the suffix ".sha1" rather than ".sha"
Actually the suffix should be ".sha" and not ".sha1". See the "not
normative" policy (a recommendation? :-) described in
http://www.apache.org/dev/release-signing.html#policy.
BR,
Jukka Zitting
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org