[jira] [Commented] (LOG4NET-556) Rolling file appender only recognises dates in yyyy-MM-dd format.

2017-03-07 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900855#comment-15900855 ] ASF GitHub Bot commented on LOG4NET-556: GitHub user Snotface opened a pull reque

[GitHub] log4net pull request #43: LOG4NET-556 - Allow for dates that aren't necessar...

2017-03-07 Thread Snotface
GitHub user Snotface opened a pull request: https://github.com/apache/log4net/pull/43 LOG4NET-556 - Allow for dates that aren't necessarily in the -MM-dd format. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Snotface/log4n

[jira] [Created] (LOG4NET-556) Rolling file appender only recognises dates in yyyy-MM-dd format.

2017-03-07 Thread Steven Nicholas (JIRA)
Steven Nicholas created LOG4NET-556: --- Summary: Rolling file appender only recognises dates in -MM-dd format. Key: LOG4NET-556 URL: https://issues.apache.org/jira/browse/LOG4NET-556 Project: Log4

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

2017-03-07 Thread Stefan Bodewig
On 2017-03-08, Matt Sicker wrote: > I may be missing some mailing lists considering I just subscribed to half > of them less than five minutes ago. > This is a vote to merge the various Apache Logging Services mailing lists. > The proposal is to combine them as follows: > log4j-dev@, log4php-dev

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

2017-03-07 Thread Matt Sicker
No wait, the lazy voting thing at Commons is just the same form we use for code, just with an email plus a 72 hour notice. Makes sense for repository changes since those are a pain to reverse once the format is changed to git. On 7 March 2017 at 23:07, Matt Sicker wrote: > The -1 thing is mentio

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

2017-03-07 Thread Matt Sicker
The -1 thing is mentioned here regarding a -1 being a veto for anything consensus-related (generally anything to do with adding or removing committers/PMCs). I suppose in that context, a mailing list change probably falls under lazy majority, though what

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

2017-03-07 Thread Ralph Goers
+1 Note that generally a -1 is a veto only on code commits. On everything else it just means you are against the proposal. However, we generally strive for consensus so great weight is given to binding votes that are opposed. Ralph > On Mar 7, 2017, at 9:23 PM, Matt Sicker wrote: > > This is

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

2017-03-07 Thread Matt Sicker
This is my +1. If this is the incorrect voting format and we need to do a 2/3 majority instead, please veto this and let me know. This situation is not spelled out in the bylaws. On 7 March 2017 at 22:20, Matt Sicker wrote: > I may be missing some mailing lists considering I just subscribed to

[VOTE] Combine the project user and dev mailing lists into user@ and dev@

2017-03-07 Thread Matt Sicker
I may be missing some mailing lists considering I just subscribed to half of them less than five minutes ago. This is a vote to merge the various Apache Logging Services mailing lists. The proposal is to combine them as follows: log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> d...@logging

[jira] [Commented] (LOG4NET-551) LockRecursionException when using File Appenders

2017-03-07 Thread Dan K (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900067#comment-15900067 ] Dan K commented on LOG4NET-551: --- Hi Stefan, This is awesome news and thank you/your team

Re: Releasing 2.0.8?

2017-03-07 Thread Stefan Bodewig
On 2017-03-07, Stefan Bodewig wrote: > On 2017-03-07, Dominik Psenner wrote: >> *hm* >> Rereading the patch its probably safe to just apply the patch [1] and >> check if all the unittests pass. >> [1] >> https://issues.apache.org/jira/secure/attachment/12852105/log4net-DebugAppenderCategory3.pa

[jira] [Resolved] (LOG4NET-553) DebugAppender configuration should give the possibility to disable outputting loggerName as category

2017-03-07 Thread Stefan Bodewig (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved LOG4NET-553. Resolution: Fixed Fix Version/s: 2.0.8 Many thanks, Jean-Francois, I've committed yo

[jira] [Commented] (LOG4NET-551) LockRecursionException when using File Appenders

2017-03-07 Thread Stefan Bodewig (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899933#comment-15899933 ] Stefan Bodewig commented on LOG4NET-551: I'll be cutting a release candidate this

Re: Releasing 2.0.8?

2017-03-07 Thread Stefan Bodewig
On 2017-03-07, Dominik Psenner wrote: > *hm* > Rereading the patch its probably safe to just apply the patch [1] and > check if all the unittests pass. > [1] > https://issues.apache.org/jira/secure/attachment/12852105/log4net-DebugAppenderCategory3.patch That's something I can do, I'll run them

Re: Releasing 2.0.8?

2017-03-07 Thread Dominik Psenner
*hm* Rereading the patch its probably safe to just apply the patch [1] and check if all the unittests pass. [1] https://issues.apache.org/jira/secure/attachment/12852105/log4net-DebugAppenderCategory3.patch On 2017-03-07 10:42, Stefan Bodewig wrote: On 2017-03-06, Dominik Psenner wrote:

[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders

2017-03-07 Thread Dan K (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897000#comment-15897000 ] Dan K edited comment on LOG4NET-551 at 3/7/17 2:22 PM: --- Upgrading s

[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders

2017-03-07 Thread Dan K (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899209#comment-15899209 ] Dan K edited comment on LOG4NET-551 at 3/7/17 2:22 PM: --- Hi Stefan,

[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders

2017-03-07 Thread Dan K (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899209#comment-15899209 ] Dan K edited comment on LOG4NET-551 at 3/7/17 2:21 PM: --- Hi Stefan,

[jira] [Updated] (LOG4NET-551) LockRecursionException when using File Appenders

2017-03-07 Thread Dan K (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan K updated LOG4NET-551: -- Hi Stefan, Update: 1) I cloned and built v2.0.8 from latest trunk to upgrade as you suggested. In our case, this

Re: Releasing 2.0.8?

2017-03-07 Thread Stefan Bodewig
On 2017-03-06, Dominik Psenner wrote: > The codereview of 553 is fine and includes reasonable unittests. The > regression tests for all supported framework targets is the bottleneck here. What kind of regression tests do you envision? Is there anything I or a different member of the community can