gmatta | 5 Aug 17:49 2011

log4net Filters


I have two log4net xml files for a project I am using.  The first is below.

<?xml version="1.0" encoding="utf-8" ?>
<log4net>

  <logger name="ValidationEngine">
    <level value="INFO"/>
    <appender-ref ref="ValidationEngine" />
  </logger>

  <appender name="ValidationEngine"
type="log4net.Appender.RollingFileAppender">

    <file value="log/ValidationEngine.txt" />
    <appendToFile value="true" />
    <rollingStyle value="Composite" />
    <datePattern value="yyyyMMdd" />
    <maxSizeRollBackups value="30" />
    <maximumFileSize value="10MB" />
    <layout type="log4net.Layout.PatternLayout">
      <Header value="BEGIN LOGGING: %date %newline"
type="log4net.Util.PatternString" />
      <Footer value="END LOGGING %newline" type="log4net.Util.PatternString"
/>

    </layout>
  </appender>

</log4net>
(Continue reading)

Curt Arnold | 9 Aug 05:34 2011
Picon

Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)

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. 

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:
(Continue reading)

Stefan Bodewig | 9 Aug 05:50 2011
Picon

Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)

On 2011-08-09, Curt Arnold wrote:

> 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)

JIRA already has 1.2.11 as release version and tons of issues assigned
to it.  20 are still open 34 are already in the resolved state.

Some triage may be in order.  34 fixed issues sounds huge and it may
very well be worth pushing back some issues without patches and release
the rest now rather than waiting for the rest.

I'm not sure we need a separate issue for the release itself when JIRA
provides the roadmap view.

> 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.
(Continue reading)

Stefan Bodewig (JIRA | 9 Aug 06:26 2011
Picon

[jira] [Created] (LOG4NET-299) Release Log4Net 1.2.11

Release Log4Net 1.2.11
----------------------

                 Key: LOG4NET-299
                 URL: https://issues.apache.org/jira/browse/LOG4NET-299
             Project: Log4net
          Issue Type: Task
          Components: Other
            Reporter: Stefan Bodewig
             Fix For: 1.2.11

Master issue to track the 1.2.11 release

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Stefan Bodewig | 9 Aug 06:27 2011
Picon

Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)

[cross-posted so people don't duplicate effort, rest should only happen
on the dev list]

On 2011-08-09, Stefan Bodewig wrote:

> On 2011-08-09, Curt Arnold wrote:

>> 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)

> I'm not sure we need a separate issue for the release itself when JIRA
> provides the roadmap view.

Created one anyway <https://issues.apache.org/jira/browse/LOG4NET-299>

Stefan

Jim Scott | 10 Aug 01:15 2011

Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)


On 8/8/2011 8:34 PM, Curt Arnold wrote:
> 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.

Curt, I am more than interested in helping this project move forward. 
However I am not 100% confident that I would be able to do things 
exactly to the standard expected so would need some guidance in 
providing help if you are interested in having me participate.

Roy Chastain | 10 Aug 01:19 2011

RE: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)

I have volunteered my services before, but unfortunately, I don't know
how to use ANY of the tools required to interface with Jira and the
source control.  I fear that I am Microsoft centric and will, for the
most part, probably stay that way.

If someone could give me good guidance, I could learn enough to be
productive.

----------------------------------------------------------------------
Roy Chastain
SOHO Technology Solutions, LLC
(770) 426-4708
http://www.sohotech.biz
If you do not wish to receive future email from SOHO Technology
Solutions, please reply to this message with the subject line of Remove
Me.

-----Original Message-----
From: Jim Scott [mailto:jscott <at> infoconex.com] 
Sent: Tuesday, August 09, 2011 19:16
To: log4net-dev <at> logging.apache.org
Subject: Re: Compiling log4net with strong name and 3rd party
dependencies (also is log4net in a cul-du-sac)

On 8/8/2011 8:34 PM, Curt Arnold wrote:
> 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.

(Continue reading)

Curt Arnold | 10 Aug 05:54 2011
Picon

Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)

Good to have both of you here. 

Hopefully the content under "Contribute back to the community" at
http://www.apache.org/foundation/getinvolved.html can get you started.

Write access to the ASF source code repository is granted by a process that requires some history of
contribution to a project, so for the time being, anyone new to contributing to log4net that doesn't
already have an Apache account will need to work by reviewing bugs and submitting patches (checkout the
source code using Subversion, look at a bug, add test cases, write a fix, do a "svn diff" to produce a
difference between your final and starting version and upload) to JIRA which is basically how almost all
people with Apache accounts earned their Apache accounts.

If bugs in JIRA have good test cases and patches, we will come up with some set of people with existing Apache
credentials to act as mentors who will review the patches and commit them.

Our current situation is those with the itch don't have the keys and those with the keys don't have the itch
(or they have too many other itches and haven't been able to get around to this particular itch).

On Aug 9, 2011, at 6:19 PM, Roy Chastain wrote:

> I have volunteered my services before, but unfortunately, I don't know
> how to use ANY of the tools required to interface with Jira and the
> source control.  I fear that I am Microsoft centric and will, for the
> most part, probably stay that way.
> 
> If someone could give me good guidance, I could learn enough to be
> productive.
> 

On Aug 9, 2011, at 6:15 PM, Jim Scott wrote:
(Continue reading)

Curt Arnold | 10 Aug 05:57 2011
Picon

Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)

By the way, no need to apologize. The ASF is an educational foundation and community which happens to
produce software.

On Aug 9, 2011, at 6:15 PM, Jim Scott wrote:

> 
> 
> On 8/8/2011 8:34 PM, Curt Arnold wrote:
>> 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.
> 
> Curt, I am more than interested in helping this project move forward. However I am not 100% confident that I
would be able to do things exactly to the standard expected so would need some guidance in providing help if
you are interested in having me participate.
> 
> 

Stefan Bodewig | 10 Aug 06:49 2011
Picon

Re: Compiling log4net with strong name and 3rd party dependencies (also is log4net in a cul-du-sac)

Hi Jim,

On 2011-08-10, Jim Scott wrote:

> On 8/8/2011 8:34 PM, Curt Arnold wrote:

>> 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.

> Curt, I am more than interested in helping this project move
> forward.

This sounds great.

> However I am not 100% confident that I would be able to do things
> exactly to the standard expected so would need some guidance in
> providing help if you are interested in having me participate.

Don't worry.

Most people around here won't know me as I'm just a user of log4net
myself and haven't contributed much to it.  In 2000 I became involved
with the Apache Software Foundation as a committer to Apache Ant - some
small build tool nobody knew back then that initially was used to build
Tomcat and was later spun out as a separate project.  Those familiar
with the Java space will know what has grown out of it.  After that I've
helped out here and there and still am a committer and PMC member at Ant
(Continue reading)


Gmane