log4net 1.2.9 was released as a beta for 2 main reasons. It had been a very long time since the 1.2 beta 8 release and there had been many fixes which needed to be release, however there were also going to be a number of new issues with the release simply due to the number of changes since 1.2 beta 8. A number of issues have been identified with 1.2.9 and these have been fixed.
The issue tracking system maintains a log of the fixes for the next release: http://issues.apache.org/jira/browse/LOG4NET?report=com.atlassian.jira.p lugin.system.project:roadmap-panel There were also some areas where the documentation was not synchronised with the code and these needed to be resolved before a final release could be made. The other reason is that log4net was, and still is, in incubation at apache. While in this state it is not possible for apache to endorse official releases of log4net. Technically it is easier to make a development or beta release of an incubating project. As far as which version of log4net to use in production the 1.2 beta 8 release has proved itself stable and the 1.2.9 release is a step up in quality over that. I would recommend using the 1.2.9 release over the previous 1.1.1 release. Cheers, Nicko > -----Original Message----- > From: Russell Haley [mailto:[EMAIL PROTECTED] > Sent: 17 June 2005 17:04 > To: Log4Net Users Group > Subject: re: 1.2.9 beta > > Okay, let me try asking this question again: > > Is l4n 1.2.9 "beta" stable enough for production applicaitons > or would I be better off using 1.1.1 from the archive list? I > would prefer not to have to use a three year old version to > avoid a beta release. That's why I asked if there is any > reason 1.2.9 is still beta... Is there a specific reason like > it must be in beta for a set time period, or a bug that > you're still working on, or is your team really particular > about what it calls "release"? > > Cheers > Russ > >
