logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <grobme...@gmail.com>
Subject ASC were missing - do we need to revote?
Date Sat, 26 May 2012 09:56:13 GMT

in the 1.2.17 RC were the asc files missing (i guess it is something
with mvn, because they are still not generated). Anyway I created them
manually like:
gpg --armor --output $file.asc --detach-sig $file

Then I uploaded them to:

Afterwards I copied the release tar.gz and zip files including asc
files to the dist folder.

$ ls -al
-rw-r--r--  1 grobmeier  logging  2864448 May 26 09:47 log4j-1.2.17.tar.gz
-rw-r--r--  1 grobmeier  logging      195 May 26 09:47 log4j-1.2.17.tar.gz.asc
-rw-r--r--  1 grobmeier  logging       32 May 26 09:47 log4j-1.2.17.tar.gz.md5
-rw-r--r--  1 grobmeier  logging       40 May 26 09:47 log4j-1.2.17.tar.gz.sha1
-rw-r--r--  1 grobmeier  logging  4764416 May 26 09:47 log4j-1.2.17.zip
-rw-r--r--  1 grobmeier  logging      195 May 26 09:47 log4j-1.2.17.zip.asc
-rw-r--r--  1 grobmeier  logging       32 May 26 09:47 log4j-1.2.17.zip.md5
-rw-r--r--  1 grobmeier  logging       40 May 26 09:47 log4j-1.2.17.zip.sha1

Now it should work well.

Then I found out how we deployed to repository.apache.org (grand
central). It was by creating a bundl articfact. This is a jar file
containing all of our release artifacts and uploading them to
repository.a.o via the web interface. This did work and now the
artifacts are staged:


I will document these steps fo course.

Question: as the ASC files were not present on the original vote, do
we need to vote again? I think no, because the artifacts are still
there and I don't consider an ASC file an release artifact.

If I don't hear any objections, i will "svn up" the logging site and
write an announcement for the new release.



To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message