Process to address Issues reported on github

Working on Issues

In preparation of the coders call on 2018-06-19 the team reviewed the time to close issues reported on github between Nov-8 2017 and June-18 2018. The average time to close was 29 days but this figure does does not reflect the effective time to address them which was shorter. It is evident that going forward, the process to handle issues needs to be streamlined. The Chairs asked the Coders Team to establish a regular process in handling issues reported on github. The working proposal -- subject to discussion by the PSE Team -- is:

(Review time until 2018-07-05)

The PSE Team invites every user to provide feedback and report issues by opening an issue in github. The Coders team is working to address those issues in a timely manner. The team is targeting to address issues within 1 week after assignment, establishing the following process.

1. Regularly review list of open issues at each weekly coders call so that

   • New issues will be labeled (prioritized) and assigned to coders during the call
   • Broader issues will be broken up into smaller ones and assigned
   • Issues that have been addressed will be closed
   • When closing an issue, we will add a statement how the issue has been addressed or why it had been rejected

2. Priority is spent on issues affecting users of the code:

   • Prio-1: Bugs found in master branch
   • Prio-2: Bugs found in Development branch
   • Prio-3: Functional and usability issues in any branch
   • Prio-4: Enhancements and other requests

3. Some issues may require more time to address

   • For prio1,2: take a quick mitigation action to avoid users entering the error condition before trying to solve
   • For prio3,4: provide a feedback and a rough estimate by when the issue can be reasonably addressed