Return-Path: Delivered-To: apmail-logging-log4cxx-user-archive@www.apache.org Received: (qmail 15413 invoked from network); 12 May 2010 15:08:00 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 May 2010 15:08:00 -0000 Received: (qmail 8193 invoked by uid 500); 12 May 2010 15:08:00 -0000 Delivered-To: apmail-logging-log4cxx-user-archive@logging.apache.org Received: (qmail 8131 invoked by uid 500); 12 May 2010 15:08:00 -0000 Mailing-List: contact log4cxx-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4CXX User" List-Id: Delivered-To: mailing list log4cxx-user@logging.apache.org Received: (qmail 8116 invoked by uid 99); 12 May 2010 15:08:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 15:08:00 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dalewking@gmail.com designates 209.85.161.47 as permitted sender) Received: from [209.85.161.47] (HELO mail-fx0-f47.google.com) (209.85.161.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 15:07:52 +0000 Received: by fxm11 with SMTP id 11so149351fxm.34 for ; Wed, 12 May 2010 08:07:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=UdKUOtW19xpAZT1tVzPH5HUUXiolQgJC2vm0pSMLTjg=; b=LsBuPuUPkeD52/Xm1aOTa/occkim7jBRItVShuFfpquMaYG2CpR5dOP7aE+q5wviRu Z0tOFLZW60OUeP7xXhRNVbdsEnCdXXjcPgXNlZ+/rAHvTqvabEneB6xVTFiJh4+Hizyg SNzniBmVevki/7+IpQK1kXNR1dx0dZf+kXTsg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=fQp/wuKvnA+2Lzwsjdi+Jnm5JYIXzqdnabPJkexXeJnRz7EeafjppLioPdbQQc9H/T uSWezO8ukzueunQQpo2SHeHR72ZsDtD17uKHm/qjCVR0QCaJT0GYFv0XYAaC5lzkil1C 2Vt8MCnFGv4QbHWEflUGarCQ65uPjj2i9nlxA= MIME-Version: 1.0 Received: by 10.223.98.83 with SMTP id p19mr1493697fan.27.1273676852326; Wed, 12 May 2010 08:07:32 -0700 (PDT) Received: by 10.223.116.72 with HTTP; Wed, 12 May 2010 08:07:32 -0700 (PDT) In-Reply-To: References: <745497DA-DF14-4B72-8461-27CA573EC75D@apache.org> Date: Wed, 12 May 2010 11:07:32 -0400 Message-ID: Subject: Re: log4cxx 0.10.1 release plan (Re: link error in release mode with Visual Studio 2008 on log4cxx-user) From: Dale King To: Log4CXX User Content-Type: multipart/alternative; boundary=0015174bef465772cc04866700f1 X-Virus-Checked: Checked by ClamAV on apache.org --0015174bef465772cc04866700f1 Content-Type: text/plain; charset=ISO-8859-1 I appreciate your work on this, but the thing that desperately needs a new release is Chainsaw! It has been over 4 years since it has been released. The current release is based on the abandoned 1.3 branch of Log4J so there are several things that do not work with the current versions of Log4J and Log4Cxx. On Wed, May 12, 2010 at 12:39 AM, Curt Arnold wrote: > Cross posting on log4cxx-user since the question was asked there. Followup > discussion should be on log4cxx-dev. > > Begin forwarded message: > > > From: Curt Arnold > > Date: May 11, 2010 11:38:19 PM CDT > > To: Log4CXX Dev > > Subject: log4cxx 0.10.1 release plan (Re: link error in release mode with > Visual Studio 2008 on log4cxx-user) > > > > > > On May 10, 2010, at 8:44 AM, Reynolds, John wrote: > > > >> Good to see you back Curt. Any dates on next release? > >> > >> I meant what executable format ( looked it up, it is Mach-O ). I knew it > wasn't ELF even though it does use the FreeBSD tools. > >> > > > > I've just logged http://issues.apache.org/jira/browse/LOGCXX-363 for a > subsequent release. If there are bugs that really should be addressed > before a release, mark it as a blocker on LOGCXX-363. If there are any bugs > that you believe that you think are ready to go, please mention them on the > list. Making VS 2010 happy would be one of them. > > > > I had really good intentions to work a log4cxx release as soon as I got > through log4j 1.2.16, but that took much longer than I expected and there > are still some aftermath issues that need to be cleaned up. > > > > Any help on prioritizing or checking the bug reports would be > appreciated. > > > > -- Dale King --0015174bef465772cc04866700f1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I appreciate your work on this, but the thing that desperately needs a new = release is Chainsaw! It has been over 4 years since it has been released. T= he current release is based on the abandoned 1.3 branch of Log4J so there a= re several things that do not work with the current versions of Log4J and L= og4Cxx.

On Wed, May 12, 2010 at 12:39 AM, Curt Arnol= d <carnold@apach= e.org> wrote:
Cross posting on log4cxx-user since the question was asked there. =A0Follow= up discussion should be on log4cxx-dev.

Begin forwarded message:

> From: Curt Arnold <carnold@ap= ache.org>
> Date: May 11, 2010 11:38:19 PM CDT
> To: Log4CXX Dev <= log4cxx-dev@logging.apache.org>
> Subject: log4cxx 0.10.1 release plan (Re: link error in release mode w= ith Visual Studio 2008 on log4cxx-user)
>
>
> On May 10, 2010, at 8:44 AM, Reynolds, John wrote:
>
>> Good to see you back Curt. Any dates on next release?
>>
>> I meant what executable format ( looked it up, it is Mach-O ). I k= new it wasn't ELF even though it does use the FreeBSD tools.
>>
>
> I've just logged http://issues.apache.org/jira/browse/LOGCXX-36= 3 for a subsequent release. =A0If there are bugs that really should be = addressed before a release, mark it as a blocker on LOGCXX-363. =A0If there= are any bugs that you believe that you think are ready to go, please menti= on them on the list. =A0 Making VS 2010 happy would be one of them.
>
> I had really good intentions to work a log4cxx release as soon as I go= t through log4j 1.2.16, but that took much longer than I expected and there= are still some aftermath issues that need to be cleaned up.
>
> Any help on prioritizing or checking the bug reports would be apprecia= ted.
>




--
Dale King

--0015174bef465772cc04866700f1--