Re: Moving forward with updates, builds and versions

Hi Stefan and Roy, sorry for the late response. This sunny sunday took me for a trip into the mountains. :-) See the inlines below. > The normal state of an ASF project is that all people who contribute > code on a regular basis have write access - if they want it. I would not advise to commit t

Re: Moving forward with updates, builds and versions

I forgot to say that this workflow works just great even for the time we have no write privileges on the SVN repository. The changesets will be stuck at "log4net-crew", waiting there to be pushed to the svn repository. Best regards -- Dominik Psenner ## OpenPGP Key Signature #

Re: Discussing the existing patches

On 08/13/2011 04:58 PM, Stefan Bodewig wrote: > Absolutely. I'm running out of time right now, but will focus on the > three issues you've mentioned soon. Great! Here there are the patches: https://bitbucket.org/NachbarsLumpi/log4net-patches You can review them by enabling the patchqueue extens

Re: Open issues for 1.2.10 release

On 08/13/2011 04:46 PM, Stefan Bodewig wrote: > I'm not even sure whether some of them still are relevant. They > certainly need to be rescheduled. > > My preference would be to have some release like 1.2.MAINTNENANCE that > we'd assign things to that may eventually get fixed in a 1.2.x release >

Re: Moving forward with updates, builds and versions

I currently have commit rights and I'm working the process right now to add additional help though the process takes a certain amount of time. Expect an announcement on Wednesday. Code development at the ASF should be done in the open and not in a private branch that unveiled to the community (

Re: Moving forward with updates, builds and versions

On 2011-08-14, Dominik Psenner wrote: > sorry for the late response. This sunny sunday took me for a trip into > the mountains. :-) See the inlines below. I live further up north in Germany (guessing from your name) so it hasn't been as sunny around here 8-( >> The normal state of an ASF project

Re: Moving forward with updates, builds and versions

On 2011-08-15, Curt Arnold wrote: > Code development at the ASF should be done in the open and not in a > private branch that unveiled to the community (has happened in the > past) as that basically prevents anyone else from influencing the work > while in process. To be fair, this is not what Do

[jira] [Updated] (LOG4NET-285) Issue with rolling based on a date

[ https://issues.apache.org/jira/browse/LOG4NET-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-285: --- Fix Version/s: (was: 1.2.10) 1.2.11 > Issue with rolling based on a d

[jira] [Updated] (LOG4NET-227) create a more directory when log files.

[ https://issues.apache.org/jira/browse/LOG4NET-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-227: --- Fix Version/s: (was: 1.2.10) 1.2.11 > create a more directory when lo

[jira] [Updated] (LOG4NET-274) log4net doesn't log when running a .Net 4.0 Windows application built in Release mode

[ https://issues.apache.org/jira/browse/LOG4NET-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-274: --- Fix Version/s: (was: 1.2.10) 1.2.11 > log4net doesn't log when runnin

[jira] [Updated] (LOG4NET-236) Request URL PatternConverter

[ https://issues.apache.org/jira/browse/LOG4NET-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-236: --- Fix Version/s: (was: 1.2.10) 1.2.11 > Request URL PatternConverter >

[jira] [Updated] (LOG4NET-258) Event Log Appender or Thread Context property. Please add ability to dynamically set Category, User, and other Event Viewer properties using the Thread Contex or anothe

[ https://issues.apache.org/jira/browse/LOG4NET-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-258: --- Fix Version/s: (was: 1.2.10) 1.2.11 > Event Log Appender or Thread Co

[jira] [Updated] (LOG4NET-221) Store log in database using log4net

[ https://issues.apache.org/jira/browse/LOG4NET-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-221: --- Fix Version/s: (was: 1.2.10) 1.2.11 > Store log in database using log

[jira] [Updated] (LOG4NET-237) URL Referrer Pattern Converter

[ https://issues.apache.org/jira/browse/LOG4NET-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-237: --- Fix Version/s: (was: 1.2.10) 1.2.11 > URL Referrer Pattern Converter

[jira] [Updated] (LOG4NET-211) Log4net with MS Access 2007 for asp.net 3.5 website

[ https://issues.apache.org/jira/browse/LOG4NET-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-211: --- Fix Version/s: (was: 1.2.10) 1.2.11 > Log4net with MS Access 2007 for

[jira] [Updated] (LOG4NET-235) IP Address Pattern Converter

[ https://issues.apache.org/jira/browse/LOG4NET-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-235: --- Fix Version/s: (was: 1.2.10) 1.2.11 > IP Address Pattern Converter >

Re: Open issues for 1.2.10 release

On 2011-08-13, Dominik Psenner wrote: > There are 9 open issues targeted for 1.2.10. They should probably be > rescheduled to be included in 1.2.11? I've just been granted enough JIRA karma to at least re-assign those issues to 1.2.11 (but can't create new versions, yet). Without even reading th

Client Profiles (was Re: Open issues for 1.2.10 release)

On 2011-08-15, Dominik Psenner wrote: > The other big story is the support for the .NET client profiles. As I > understood it, we have to drop everything in log4net that is not > supported in a .NET 4.0 client profile (i.e. references to System.Web). > To achieve this we have at least two options: