sebb wrote:
On 18/11/2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi

This is the second attempt to release commons-logging 1.1.1.

Changes since the last try:
- The Maven 2 build now packages LICENSE and NOTICE files in the correct
place in all distributables
- A couple of minor bugs were fixed

Release Notes:
http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310484&styleName=Html&version=12312160

Tag:
https://svn.apache.org/repos/asf/commons/proper/logging/tags/commons-logging-1.1.1/

Staged repository:
http://people.apache.org/~dennisl/staging-repository-commons-logging/

Not sure why there are MD5 and SHA1 checksums of the .ASC files -
surely they are redundant?

This is handled by the gpg-plugin in Maven 2. According to the docs these files should be excluded. If there is no bug report for it I'll create one.

 Also, it would be nice if the MD5 files had the file name in them.

This is handled automatically by Maven. It uses the "quiet" format by default. I'm not sure if it is possible to change this. The quiet format is used for everything that goes into the Central repository.

Distribution files:
http://people.apache.org/~dennisl/commons-logging-1.1.1.tar.gz
http://people.apache.org/~dennisl/commons-logging-1.1.1.tar.gz.asc
http://people.apache.org/~dennisl/commons-logging-1.1.1.zip
http://people.apache.org/~dennisl/commons-logging-1.1.1.zip.asc

No MD5 or SHA1 files at all here - there should be at least one or the
other for the zip and .tar.gz files

I haven't released anything that uses the traditional distribution channel before, so I wasn't sure what was needed.

I have created MD5 and SHA1 checksums:
http://people.apache.org/~dennisl/commons-logging-1.1.1.tar.gz.md5
http://people.apache.org/~dennisl/commons-logging-1.1.1.tar.gz.sha1
http://people.apache.org/~dennisl/commons-logging-1.1.1.zip.md5
http://people.apache.org/~dennisl/commons-logging-1.1.1.zip.sha1



Please cast your votes!

[ ] +1, Let's do it
[ ] -1, Nah


Here's my +1

--
Dennis Lundberg


--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to