Oompa, Loompa, doom-pa-dee-do
I have a perfect puzzle for you
Oompa, Loompa, doom-pa-dee-dee
If you are wise, you’ll listen to me
When submitting a bug report, the preferred template is as follows:
- Brief description
- Steps to reproduce
- Expected results
- Actual results
Description:
Be brief.
Do not insert your own theory as to why something doesn’t work. This throws the developer off. Example: I do X, expect Y, but instead I get Z, therefore “Renoise doesn’t accept booleans”. In the developer’s mind, because the very specific problem is booleans, he looks there first, sees there’s nothing wrong, ignores the rest. If you keep doing this it turns into “boy who cries wolf” syndrome, and people stop listening…
Steps to reproduce look like this:
- Launch Renoise
- Open the demo song “Vivace - Jong Belegen”
- Press spacebar
- Click the Pattern Matrix Button
- …
The more precise the better, the less precise the shittier.
Expected results:
You expect something to happen. Describe it here.
Actual results:
Instead, something else happens, and this is wrong. Describe it here.
Extras:
Don’t post a bug report as a reply to some thread. Instead, start a new thread. This ensures someone actually looks at your issue.
Screenshots make the bug report 1000 times better. A video capture makes the bug report 100000 times better.
Price of Renoise at the time of purchase. E.g. when I pay for a coffee, I’m not paying for a future cup of coffee those are bonus, they are not the product at the time of purchase: ~58€. Reasonable cost of fixing the average bug in software industry: A day of work (8 hours) * 40€ = ~320€ Probable Renoise developer salary? Below minimum wage living in a squat. Enthusiasm for fixing poorly explained bugs with flamewar undertones at the same time as developing awesome new community driven features for next to nothing: 0.
Oompa, Loompa, doom-pa-dee-da
Given good manners, you will go far
You will live in happiness too
Like the Oompa Loompa doom-pa-dee-do
Pitch in to win.
