The version of Apache log4j used by SoundHelix.

[[ 🗃 ^aEp6o apache-log4j ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]

Clone

HTTPS: git clone https://vervis.peers.community/repos/aEp6o

SSH: git clone USERNAME@vervis.peers.community:aEp6o

Branches

Tags

v1_2_15_rc1 :: src / xdocs /

plan.xml

<?xml version="1.0" encoding="iso-8859-1"?>
<!--
 Licensed to the Apache Software Foundation (ASF) under one or more
 contributor license agreements.  See the NOTICE file distributed with
 this work for additional information regarding copyright ownership.
 The ASF licenses this file to You under the Apache License, Version 2.0
 (the "License"); you may not use this file except in compliance with
 the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.

-->
<document>

  <properties>
    <author email="not@disclosed">Ceki G�lc�</author>
    <author email="not@disclosed">Mark Womack</author>
    <author email="not@disclosed">Curt Arnold</author>
    <title>Release roadmap for log4j</title>
  </properties>

  <body>

    <section name="The Roadmap">

      <p>This page documents that roadmap and gives you an idea of what
      to expect from future versions and timeframes for release.
      </p>
      
      <p>Our users keep inventing better ways and adding new
      requirements. The downside is that our todo list keeps
      growing. The upside is that there is plenty of work to go
      around. If you are interested in participating, send an email
      on the log4j-dev@ mailing list stating your interest. You'll
      be promptly enrolled.  We're always looking for help!  Don't be
      put off if in the "Volunteer" column already has a person
      listed. Programming is fun, especially if it is done in a
      team.
      </p>

    </section>

    <section name="Release 1.2.16">
      <p>Expected timeframe: As needed</p>
      
      <p>log4j 1.2.15 was released in March 2007.  log4j 1.2 is continuing to be maintained
	  in response to reported issues and requests for back-ported features from log4j 1.3.</p>
    </section>
    
    <section name="Release 1.3">
      <p>Expected timeframe: indeterminate</p>
	  
	  <p>Compatibility with earlier releases (as implied by a minor verion number change) was not enforced during the 
	  development process and much of the recent effort has been to restore compatibility.  However, it does not
	  seem likely that log4j 1.3 will ever been sufficiently compatible with log4j 1.2
	  to recommend it as a general replacement for log4j 1.2.  Additional alpha releases are expected,
	  however it is possible that the development focus may shift to log4j 2.0.</p>
	  
    </section>

    <section name="Release 2.0">
      <p>Expected timeframe: indeterminate</p>
      
      <p>log4j 2.0 is still conceptual but would be designed for Java 5 and later,
	  would use be designed for fine-grain concurrency to maximize performance on
	  multi-processor systems, would minimize exposure of implementation details and
	  adhere to current Java coding practices.  The design of log4j 2.0 may attempt to
	  support javax.util.logging by allowing, for example, a log4j 2.0 Appender to serve
	  as a javax.util.logging.Handler.  log4j 2.0 would likely be modularized, possibly using
	  OSGi and would include a facade that emulates the log4j 1.3 API but would not be compatible
	  with user written appenders and other components.</p>
    </section>
     
  </body>

</document>
[See repo JSON]