On Jul 1, 2010, at 12:11 AM, Scott Deboy wrote: > > I actually don't have a pgp signature on file here, so I don't think I can > cut release candidates myself without going through some hoops, so I've been > relying on Curt's free time, but I should probably just figure out what I > need to do to cut the release candidates myself... > > Scott
"Free time", I'm not sure I know what that means. Sorry, been buried recently. As far as I can tell, everything is ready on log4j and the companions for a release candidate cut. Can you describe the JDK 1.5 dependency in receivers? Does it require JDK 1.5+ to build, but some aspects might function on earlier VM's or it is cross the board failure on earlier JDK's. The last couple of builds have been on Ubuntu, less to collect than trying to build on Windows. I was intending to build the last log4j release on bootable CD or Amazon Web Services to make it easy for someone else (or me if I had a crash) to create a near duplicate release. I had to update my signing key during the 1.2.16 and it took a couple of tries to get the signature in everyplace that it needed to be. Even if you don't actually put the bits on the distribution server, it would be good to have someone else walk through the process. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
