[jira] [Commented] (SINGA-417) Adding security channel

[ https://issues.apache.org/jira/browse/SINGA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850948#comment-16850948 ] ASF subversion and git services commented on SINGA-417: --- Commit

[jira] [Commented] (SINGA-417) Adding security channel

[ https://issues.apache.org/jira/browse/SINGA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825124#comment-16825124 ] ASF subversion and git services commented on SINGA-417: --- Commit 1858046 from Moaz

[jira] [Commented] (SINGA-417) Adding security channel

[ https://issues.apache.org/jira/browse/SINGA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718653#comment-16718653 ] ASF subversion and git services commented on SINGA-417: --- Commit

[jira] [Commented] (SINGA-417) Adding security channel

[ https://issues.apache.org/jira/browse/SINGA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718652#comment-16718652 ] ASF subversion and git services commented on SINGA-417: --- Commit

[jira] [Commented] (SINGA-417) Adding security channel

[ https://issues.apache.org/jira/browse/SINGA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713878#comment-16713878 ] Moaz Reyad commented on SINGA-417: -- The dev@ list is public while the security channel should be

[jira] [Commented] (SINGA-417) Adding security channel

[ https://issues.apache.org/jira/browse/SINGA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713876#comment-16713876 ] wangwei commented on SINGA-417: --- shall we use the dev@ list instead of creating a new security@ list? I