On Feb 18, 2010, at 9:03 AM, Christian Grobmeier wrote:

> Hi,
> 
> just looked into it - first glimpse showed me version 1.2.15 on
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/download.html
> Is this ok and changed while go live?
> 

Already changed in the site source.  I realized after cutting RC1 that I needed 
to replace my signing key which is documented on that page.  Then I saw that I 
had not updated the version on the page.


> On: 
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/roadmap.html
> It sounds a bit strange when it comes to:
> "Any major new features for log4j 1.2 are likely to be developed as
> companion products for log4j 1.2."
> What does it actually mean?
> 

I'll clarify that.

> On:
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/manual.html
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/publications.html
> there are character encoding problems
> 

I believe that is due to SVN sending response headers on the HTTP request 
specifying ISO-8859-1.  The files are UTF-8 encoded and declare themselves as 
such internally, but browsers trust the HTTP headers more than the content.   
The files display themselves properly when opened locally or opened from 
http://logging.apache.org which does not specify an encoding in the headers.

> I would think the benchmark can stay in as long as we have not a better one
> 
> So far from me :-) Thanks for the work!
> Christian
> 
> 
> 
> On Thu, Feb 18, 2010 at 3:39 PM, Curt Arnold <carn...@apache.org> wrote:
>> The scuttled 1.2.16 RC1 updated the staging site 
>> (http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html).
>>   I would not anticipate any structural changes, but we have a short window 
>> where we could make some content changes, such as removing the obsolete 
>> benchmark for JDK 1.3 on  log4j 1.2 landing page.  I would appreciate any 
>> reviews of the site while there is still time to change what goes out with 
>> 1.2.16 and what will likely stay in public view for a while.
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>> 
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> 


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

Reply via email to