waku-org
/
pm
mirror of https://github.com/waku-org/pm.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #91 from waku-org/non-epic-issues

This commit is contained in:
fryorcraken 2023-09-22 11:47:39 +10:00 committed by GitHub
parent b973631725 249d436a20
commit 6bdad235bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.github/labels.yml vendored
View File

@ -20,9 +20,6 @@
- name: invalid
description: This doesn't seem right
color: e4e669
- name: question
description: Further information is requested
color: d876e3
- name: wontfix
description: This will not be worked on
color: ffffff
@ -47,6 +44,9 @@
- name: release-notes
description: Issue/PR needs to be evaluated for inclusion in release notes highlights or upgrade instructions
color: fb3c99
- name: dependencies
description: Pull requests that update a dependency file or issues that track it
color: 0366d6
# Tracks
- name: track:rln

10
README.md
View File

@ -46,6 +46,7 @@ An _Epic_:
- MUST have a matching GH issue in the https://github.com/waku-org/pm with `epic` label assigned.
- MUST have a label with format `E:<epic name>` created across all relevant https://github.com/waku-org/ repos (see [labels.yml](./.github/labels.yml)).
- SHOULD be added to a GH Milestone.
- SHOULD have a `Planned Start` and `Due Date` set (these are GitHub projects fields you can find in the `Projects` section of the issue view sidebar).
- MAY list _Tasks_ present in other repos.
A _Task_:
@ -56,6 +57,15 @@ A _Task_:
- that MUST be labelled with related _Epic_ label (`E:...`),
- MUST have an _acceptance criteria_ and/or a list of _tasks_ (that can be other GH issues).
Finally, for _Tasks_ that do not belong to a given _Epic_ or _Milestone_:
- MUST have either labels:
- `bug`: This is a bug, likely reported by a user
- `enhancement`: This is an enhancement out of the scope of the technical roadmap, likely reported by a user
- Major enhancements should be carefully reviewed and prioritized.
- `documentation`: Documentation improvement or correction.
- `dependencies`: Upgrade dependencies in a timely manner to avoid time wasting when the dependency upgrade becomes critical.
Which means, in terms of _navigation_:
- Work for a Milestone is described in the related GitHub issue and tracked in the GitHub milestone.