Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Sep 19, 2016

See SafeDelete definition

It seems that new static analyzer exhumes lots of ancient legacy. Do I (we) need to give attention to such cases?

And it seems that there is no "Issues" tab in this repository. I have got some suspicious places and I'm not sure how to fix them.

@pcanal
Copy link
Member

pcanal commented Sep 20, 2016

And it seem that there is no "Issues" tab in this repository. I have got some suspicious places and > I'm not sure how to fix them.

Indeed we only use github for merge request. Issues are being tracked in JIRA at:

https://sft.its.cern.ch/jira/issues/?jql=project%20%3D%20ROOT

To create an issue: https://sft.its.cern.ch/jira/secure/CreateIssue.jspa?pid=10010&issuetype=1

See also https://root.cern.ch/guidelines-submitting-bug

@pcanal
Copy link
Member

pcanal commented Sep 20, 2016

merged. Thanks.

@pcanal pcanal closed this Sep 20, 2016
@ghost
Copy link
Author

ghost commented Sep 22, 2016

@pcanal any advice on how to report about dozen of small errors ~1 line of code each? 1 issue for all or 1 issue per error?

@pcanal
Copy link
Member

pcanal commented Sep 22, 2016

I would recommend one merge request with one commit per category of issues.

@ghost
Copy link
Author

ghost commented Sep 22, 2016

I was asking about reporting issues I don't know how to fix...

@pcanal
Copy link
Member

pcanal commented Sep 22, 2016

Then one JIRA issue/ticket per category of problems or 1 issue per error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant