# Improvements for Notary Project Planning ## Issue Lifecycle See [Issue Lifecycle](https://github.com/notaryproject/.github/blob/3881cd38a6ab10d8f950a70f7f80e1a73b4bdb29/CONTRIBUTING.md#issue-lifecycle) ## Process of triage - Maintainers (Repo or .github) are responsible to drive triage weekly, and share the results in slack channel. Futher discussion can be scheduled in community meeting if needed. ## Stale issues or PRs Clean up [stable issues or PRs](https://github.com/notaryproject/.github/blob/3881cd38a6ab10d8f950a70f7f80e1a73b4bdb29/CONTRIBUTING.md#stale-issues-or-prs) ## Labels Clean up [labels](https://github.com/notaryproject/.github/blob/3881cd38a6ab10d8f950a70f7f80e1a73b4bdb29/CONTRIBUTING.md#labels) ## Milestones Use the following milestones: - `future`: This milestone includes issues that are valuable but are not currently planned for release. We can consider the issues in the `future` milestone as our backlog. The issues in the future milestone will be reviewed on a regular basis to keep it up-to-date. For example，future milestone is reviewed at the beginning of a new release cycle. - `<release version>`: This milestone includes issues that will be released. For example, `v1.1.0`, `v1.2.0`. Deprecate the `discuss` milestone and use label `question` for issues or PRs that need further information or discussion.