Skip to content

Styling and wordsmithing updates to bug proposal#1

Open
evankanderson wants to merge 2 commits into
akashrv:bugproposalfrom
evankanderson:bug-cleanup
Open

Styling and wordsmithing updates to bug proposal#1
evankanderson wants to merge 2 commits into
akashrv:bugproposalfrom
evankanderson:bug-cleanup

Conversation

@evankanderson
Copy link
Copy Markdown

Some formatting updates to the bug proposal.

It was easier to send as a PR than to try to make them inline.


- Keep a low bug count. Bug count should not be consistently increasing release over release esp [priority/important-longterm](#Bug-priorities).
- Process shouldn't be taxing for a single person or the team.
- Maintain high product quality.
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved this to the top of the list.

- Submit new bugs anytime by creating a new issue of type “Bug”.
- Please fill the bug template and optionally propose a priority.
- All new bugs will be labelled “kind/bug” as part of the template
Bugs will be triaged weekly (this could be modified based on incoming bugs
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pretty sure this had lost the <LI> item. The others were some quoting fixes and clarification that the release target for bugs was tracked using milestones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant