Was thinking lately that the issue triaging process is currently: 1. User files issue 2. Eric triages the issue to either a release or a backlog 3. Release nanny for a particular release fixes bug, asks someone else to fix the bug or is just sits there
In the case of 'it just sitting there' a lot of user issues come in that are mostly ignored due to the release nanny's other responsibilities. I would like to get more eyes on the issues and spread the effort to not just Eric and the release nanny for a given release. Any thoughts on a weekly triage meeting? The goals would be: * assign issues to a given release or the 'backlog' * assign issues to be fixed to developers (for current releases) * Assign user reported issues to be determined if they are actually bugs or environment issues. This would spread the fixing of bugs to other people and hopefully get user issues solved more quickly. Initially I would likely just have an open invite to anyone that wants to come and may pare it down to some sort of rotation depending on the number of people that join. We would probably limit it to 1 hour per week. Thoughts? -Justin -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
