Goals
- Clean up ParaView’s issue tracker
- Evaluate as many issues as we can in the ParaView GitLab Issue tracker to verify whether they
- have been fixed or are no longer relevant
- are still present as an issue in the latest release of ParaView
- Close issues that have been fixed or are no longer relevant
- Label issues that remain as confirmed and note the version of ParaView used to confirm that the issue remains
Agenda
Start time: 12:00 GMT (8:00AM EDT, 13:00 CET)
End time: 4:00 GMT (12:00PM EDT, 15:00 CET) or until we run out of energy
12:00 GMT: Welcome and greetings
12:05 GMT Discuss plan and workflow
12:10 GMT Start working
Workflow
- Go to issues sorted by last update date. This is a list of issues for the hackathon with no Assignee.
- Pick an issue and open it in a full web page (otherwise it may disappear once you start editing it). Assign it to yourself.
- Review the issue
- If the issue has clear information to reproduce it and you cannot, close it and add the label ‘resolution:unreproducible’. Also add the ParaView version tag (‘v6.0.0’, ‘v6.0.1’, ‘v6.1.0-RC1’) – not the Milestone
- If the issue is reproducible with the information given in the issue description and comments
- Add the ‘triage:confirmed’ label
- Add the label of the ParaView version you used to confirm (v6.0.0, v6.0.1, v6.1.0-RC1). If you are testing a build from master, use the label v6.1.0-RC1.
- If the issue refers to a feature of ParaView that no longer exists, add the version label and close the issue with a note explaining that the feature no longer exists. Add the label ‘resolution:irrelevant’
- If the issue lacks sufficient information for testing, add the ‘triage:needs-info’ label.
- If unsure of an issue’s status, please discuss it with the group
- If the issue will remain open and you do not plan to fix it, remove all assignees
Physical Event