So, you are saying that those members are eager to see new features, new
functionalities and new code added to the project? Why they are not
eager to see a unit test being fixed or a dependency with a severe
security risk being removed? It is not that their original PR would be
closed as a
Comments inline:
> On 9/10/17 23:40, Priyanka Gugale wrote:
>
>> It's good idea to check for vulnerabilities, but as Pramod said all
>> softwares / libraries are going to have some or other vulnerability at any
>> time. I will go with approach of "let's discuss this addition" and we
>> should
Please see my comments inline.
Thank you,
Vlad
On 9/10/17 23:40, Priyanka Gugale wrote:
It's good idea to check for vulnerabilities, but as Pramod said all
softwares / libraries are going to have some or other vulnerability at any
time. I will go with approach of "let's discuss this addition"
[
https://issues.apache.org/jira/browse/APEXMALHAR-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanka Gugale resolved APEXMALHAR-2535.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> Timeouts in AbstractEnricher
[
https://issues.apache.org/jira/browse/APEXMALHAR-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanka Gugale reassigned APEXMALHAR-2535:
---
Assignee: Tushar Gosavi
> Timeouts in AbstractEnricher specified as int
It's good idea to check for vulnerabilities, but as Pramod said all
softwares / libraries are going to have some or other vulnerability at any
time. I will go with approach of "let's discuss this addition" and we
should not affect PRs which are not adding any new dependencies (due to old
