Issue reporting and tracking

Development
7

Your analysis is really interesting and complete @riban! I think we can take a good bunch of ideas from it and for sure that it will help to improve zynthian’s development workflow. Thanks a lot!!

Of course, we must avoid too much “burocracy”, because our development resources are precious and we shouldn’t spend too much time doing management tasks. Not to mention that programming is more funny :wink:

So, trying to take the key ideas from the last days discussion, while keeping the “low burocracy mantra” in my mind, i have a decent proposal to improve the current issue tracking:

As you can see, i removed repo’s kanbans. Now we have only the global kanban, that can be filtered easily. We also have a global issue list, and per-repo issue lists.

The workflow should be:

  1. Issue creation: Only from the zynthian-issue-tracking repo!
  2. Triage: Assign initial tags and move to the right code-repo for deeper analysis and hopefully, solving.
  3. Resolution: Awaiting => Analysis => Work in Progress => Testing => Done

Note that:

  • The new kanban have these columns:

    • New
    • Freezer
    • Awaiting
    • Analysis
    • Work in Progress
    • Testing
    • Done

  • Issue templates are used for creatiing “bug reports” and “feature requests”. Questions are redirected to forum.

Thanks

1 Like