Hi, >> Well :-) I think november is good, but we need to disucss were the >> release must go and such. Next week I am travelling lots, but lets >> start discussion then. I also wrote an e-mail in the past about this > > Come on guys, it's getting boring again :-) And we're so close before a > release!
Yeah, I agree, lets do it! I added a new wikipage, were we can nail down the already agreed items. Its there: http://wiki.apache.org/logging/Log4PHP/Log4PHPReleasePlan >> - create tag 2.0 > > svn copy . https://svn.apache.org/repos/asf/incubator/log4php/tags/2.0 > >> - create package with maven > > mvn site > That creates target/pear/log4php-2.0.0.tgz > >> - sign/hash with gpg and a key, whose public counterpart can be found >> in the repository > > gpg --detach-sign --armor target/pear/log4php-2.0.0.tgz > > What is "the repository"? My key 86A118E6 is on wwwkeys.de.pgp.net, > would that be enough? You need to create a key just for apache codesigning. However, I have one which is already signed by others. I also used it for Commons Compress. See also: http://www.apache.org/dev/release-signing.html We need a place to store our public keys on the repostiory - Gavin, do you have an idea were to store it? >> - upload the whole to a staging server > > How's that done? SCP -. but WHERE? :-) > I guess one of the mentors has to do this? No, we can do it ourselves too. Since I am also in the temp. PMC, I will probably have the right to do it. >> - after successful voting, copy the staged artifacts to the download >> server > > How? Where?? :-) > If we have a pear repository by then, upload there, too. > >> - update website with new download links > > How? Checking updated .apt page into trunk - rest is automatically >> - send announcement to user, dev and incubator list > > ... and to the blog! Agreed! Mentors, can one please advise were we can find information about locations? Otherwise i will ask on the incubator list Any more comments? Thanks Christian
