Closed adiroiban closed 8 years ago
needs-review
needs-review
IMO using priority to have a distinction between critical and minor bugs is good enough.
I fixed a small typo, the content in general is good to me.
changes-approved
changes-approved
All in all it's good.
A better distiction betweekn bugs and known-issues might help. What I mean is that they are clearly both defects but for a known issue we either decided to live with it or we cannot easily fix it or there is a workaround for it.
We can improve later anyway.
changes-approved
Scope
This adds a dedicated page for our defects and tech-debt process.
Why we got into this (5 whys)
Changes
Added initial draft.
As a drive by I have re-arranged the order of pages.
How to try and test the changes
reviewers: @alibotean @brunogola @lgheorghiu
Changes can be observed here http://styleguide.chevah.com/bugs-and-tech-debt.html
Please feel fee to make the edits directly on this branch.
This is just a brain dump so feel free to fix typos or rephase or add more clarifications.
Please suggest if we should split the defects into bugs and known-issues or some other name to make a distinction between critical bugs and all other minor bugs...we can also use priorities or other keyworks... no need for a different type.
@brunogola one reason why we don't use the Jekyll infra provided by GitHub is that with the current infra we can publish the public site from any branch.
Thanks!