+1
With the following comments (all of which are carried over from 1.2.9
and should have been mentioned earlier):
The ls-logo.jpg is always fetched from http://logging.apache.org/
images, not from ./images like the other images. ls-logo.jpg would
need to be added to the docs/images direct
On Jun 19, 2005, at 5:26 PM, Yoav Shapira wrote:
Hi,
Hmm, I could swear the Releases section in http://www.apache.org/
dev/ had a
thing about PGP usage. Basically, by signing a release you vouch
that it's
legit.
Yoav Shapira
Maybe you were thinking of one of these:
http://www.apache
ECTED]
> -Original Message-
> From: Paul Smith [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 19, 2005 6:00 PM
> To: Log4J Developers List
> Subject: Re: [VOTE] log4j 1.2.11 Release
>
> +1
>
> Thanks for all your hard work Mark.
>
> Re: PGP, is there a "
+1
Thanks for all your hard work Mark.
Re: PGP, is there a "PGP for newbies link" that's worth reading? I
wouldn't mind just understanding how it all works within ASF.
cheers,
Paul
On 19/06/2005, at 10:51 AM, Mark Womack wrote:
1) Update source files to Apache 2.0 license header.
DONE
+1
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Sun 6/19/2005 11:08 AM
To: Log4J Developers List
Cc:
Subject:Re: [VOTE] log4j 1.2.11 Release
At 05:51 PM 6/18/2005 -0700, you wrote:
>If this version is accepted, then after LS PMC appro
At 05:51 PM 6/18/2005 -0700, you wrote:
>If this version is accepted, then after LS PMC approval, then we will move
>it to the apache mirrors and update the LS website. I am going to need some
>help in creating MD5 versions of the release images as I have not done that
>before.
>
>+1
>
>-Mark
>
ROTECTED]
> Sent: Saturday, June 18, 2005 8:52 PM
> To: Log4J Developers List
> Subject: [VOTE] log4j 1.2.11 Release
>
> 1) Update source files to Apache 2.0 license header.
> DONE
>
> 2) Change jakarta references in INSTALL.txt to appropriate logging
> references.
>
1) Update source files to Apache 2.0 license header.
DONE
2) Change jakarta references in INSTALL.txt to appropriate logging
references.
DONE
3) docs dir in release images should be referring to 1.2.11 instead of
1.2.9.
DONE
4) Give docs dir a thorough once over to make sure all is valid.
D
