[jira] [Commented] (LOG4NET-406) Log4Net breaks the Microsoft naming rules for namespaces

[ https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13830995#comment-13830995 ] Ben commented on LOG4NET-406: - Yes, I understand that this is an API breaking change and yes

[jira] [Commented] (LOG4NET-406) Log4Net breaks the Microsoft naming rules for namespaces

[ https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831054#comment-13831054 ] Stefan Bodewig commented on LOG4NET-406: I'm really on the fence here, but the

[jira] [Commented] (LOG4NET-406) Log4Net breaks the Microsoft naming rules for namespaces

[ https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831129#comment-13831129 ] Ben commented on LOG4NET-406: - I guess this would make sense since you want people to

[jira] [Commented] (LOG4NET-406) Log4Net breaks the Microsoft naming rules for namespaces

[ https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13830104#comment-13830104 ] Jonathan Choy commented on LOG4NET-406: --- As a design guideline, this is a guidance,

[jira] [Commented] (LOG4NET-406) Log4Net breaks the Microsoft naming rules for namespaces

[ https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13827613#comment-13827613 ] Dominik Psenner commented on LOG4NET-406: - This is a API breaking change and we