Epic - Improve SDLC

[zanete]

User Story

As a core developer I want a clear process for SDLC so that I we don’t block each other, do throw away work and maintain developer velocity

Scope

MED - Document a processes to triage bugs as high, medium or low.

• Define process for categorizing bugs into H, M, L severity #588
• Add bug triage call to core team weekly calendar #587
• Add labels for needs-triage, fix-now, fix-later and won't-fix to Github repositories #589

LOW - Document our bug reporting requirements and create an issue template which meets them.

• Refine bug reporting guidance documentation #590
• Document our bug reporting requirements and create an issue template which meets them. #586

HIGH - Document minimum requirements for issue refinement scheduling on a sprint.

• Revise issue refinement/readiness process #613
• • It should contain at least one runnable complete manifest file for use in development and for testing/UAT.

HIGH - Document the minimum QA requirements for PRs into dev and for releases to main

• • Document the QA requirements for merging into main/release branches #632

LOW - Create if-stackblitz

• Build if-blitz #639

MISC

• Add pre-release beta to existing CI/CD to improve release process #643
• Use lint-staged for pre-commit hook in if-plugins and if #668
• Update CI in if-plugins and if-unofficial-plugins to match if #669
• Fix problem with commit lint #757
• CI/CD publishes pre-release as a last version to npm #725

[zanete]

@jawache I'm not sure if we need to create an issue for documenting the refinement process yet, let's try a couple of sprints to implement a few refinement sessions and see how that goes, perhaps there's no need to go beyond https://miro.com/app/board/uXjVKS5vX8k=/