Return-Path: 
 <log4net-user-return-5671-apmail-logging-log4net-user-archive=logging.apache.org@logging.apache.org>
X-Original-To: apmail-logging-log4net-user-archive@www.apache.org
Delivered-To: apmail-logging-log4net-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 93F94768C
	for <apmail-logging-log4net-user-archive@www.apache.org>;
 Tue,  9 Aug 2011 03:35:24 +0000 (UTC)
Received: (qmail 85411 invoked by uid 500); 9 Aug 2011 03:35:24 -0000
Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org
Received: (qmail 85041 invoked by uid 500); 9 Aug 2011 03:35:08 -0000
Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:log4net-user-help@logging.apache.org>
list-unsubscribe: <mailto:log4net-user-unsubscribe@logging.apache.org>
List-Post: <mailto:log4net-user@logging.apache.org>
Reply-To: "Log4NET User" <log4net-user@logging.apache.org>
List-Id: <log4net-user.logging.apache.org>
Delivered-To: mailing list log4net-user@logging.apache.org
Received: (qmail 84893 invoked by uid 99); 9 Aug 2011 03:35:03 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2011 03:35:03 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of curt.arnld@gmail.com
 designates 209.85.161.175 as permitted sender)
Received: from [209.85.161.175] (HELO mail-gx0-f175.google.com)
 (209.85.161.175)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2011 03:34:54 +0000
Received: by gxk3 with SMTP id 3so1314866gxk.34
        for <multiple recipients>; Mon, 08 Aug 2011 20:34:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=sender:subject:mime-version:content-type:from:x-priority
         :in-reply-to:date:content-transfer-encoding:message-id:references:to
         :x-mailer;
        bh=2YLYdDDGtb1yjD7xWUxN4ugZPvtJYNz9zl3zqY11txw=;
        b=uYtxrIposFycMtESEsK2Ynrx8aprxFUB4hrh5UCrfZmHn3jJ0Z0DBJZ+fgg855VBTa
         V0o8QFGMvZ9y6xi8TbmFbAg5lllh61A24/aJskjtu20Nw+PG9Lb1vrCLrycjkVtVZaMs
         zdfAm8A3ncXgaghAsDpPSRstSpBsvOwAO8NmQ=
Received: by 10.101.137.14 with SMTP id p14mr5287183ann.96.1312860873876;
        Mon, 08 Aug 2011 20:34:33 -0700 (PDT)
Received: from [192.168.15.24] ([50.8.45.241])
        by mx.google.com with ESMTPS id l2sm5384439anm.50.2011.08.08.20.34.32
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 08 Aug 2011 20:34:33 -0700 (PDT)
Sender: Curt Arnold <curt.arnld@gmail.com>
Subject: Re: Compiling log4net with strong name and 3rd party dependencies
 (also is log4net in a cul-du-sac)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Curt Arnold <carnold@apache.org>
X-Priority: 3
In-Reply-To: <B45039D742E9465E892BC62609CEE59C@jscottPC>
Date: Mon, 8 Aug 2011 22:34:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0059D8D-8C9A-4766-9C7F-F5C4C17C982A@apache.org>
References: 
 <CAKCk1tiMoGWRCjPZUDCXX4Dw=k=oxe=PmNhbop0+P=w9rejB2A@mail.gmail.com>
 <B45039D742E9465E892BC62609CEE59C@jscottPC>
To: Log4NET User <log4net-user@logging.apache.org>,
 Log4NET Dev <log4net-dev@logging.apache.org>
X-Mailer: Apple Mail (2.1084)

I wrote this message last night in response to the is log4net in a =
cul-du-sac thread, but it got bounced due to a spam guard which I've =
hopefully satisfied this time.   The strong naming key that has been =
used to sign log4net releases has been encrypted and can be decrypted =
using the private keys of several people including myself. I'd be happy =
to perform the release build or reencrypt the strong signing key to =
another PMC member who wants to help. However, to get to that point, it =
will take people who are motivated to pitch in and get things ready for =
release. Further discussion should be on log4net-dev.=20

My message from last night:


I'm not sure if this message got an adequate answer.

For those who want to drive a release forward, I would suggest:

Create a bug report for the next release (check if there is already one)

Make that bug dependent on any issue that you think needs to be resolved =
before the next release

If there are any debatable issues (like dropping support for earlier =
.NET versions), start a vote on the mailing list. If there are =
interrelated issues, perhaps create a page on the logging wiki and have =
a vote on all the issues in the same time.

If there are bugs without test cases or patches, create test cases and =
patches.

If there are bugs with test case and patches that should be committed, =
make a comment on the bug that it appears ready to go.

Hopefully through this process, we can develop the track record that =
will allow adding some new committers or PMC members.


On Aug 8, 2011, at 4:27 PM, Jim Scott wrote:

> From: Johannes Gustafsson
> Sent: Monday, August 08, 2011 1:20 PM
> To: log4net-user@logging.apache.org
> Subject: Compiling log4net with strong name and 3rd party dependencies
> Hi,
> =20
> There are a few bugfixes in the trunk that I need and since there has =
been no new release for a very long time, I tried to compile it myself. =
I created a key and have successfully compiled it with no problems. =
However, I have quite a few 3rd party dependencies that themselves are =
dependent on log4net. These dependencies can't find load the new =
assembly that I have created because they require that it is signed with =
a key that I dont have access to. So this means that I can't use my own =
version of log4net without recompiling all my dependencies.
> =20
> Do you have any suggestions to how I can solve this?
> =20
> Regards,
> /Johannes
> =20
> =20
> Yes, this is the same issue we have. I have a few features I would =
like to add but the thought of having to recompile everything has kept =
me from doing so.
> =20