Bug report standardization

[cpember]

I was thinking about this whilst perusing the forums looking at a lot of the crash reports and I've been on a few betas in my career, and I've found most follow this formula, and make things
a: easier to search and
b: easier for devs to make sense of

-----------
-1- build name::short bug description/title
eg: PRE-2.3 import of obj crashes octane

-2- Severity::App crash/OS crash/Feature failure/small defect/cosmetic or text error
eg: Feature failure

-3- Longer description/more detailed explanation of crash
eg: I imported some obj in to octane and i click on the thing and it crashes octane to desktop.

-4- frequency::every time you try/once and a while/hard to reproduce
eg: Application crashes every time I do this

-5- Steps to reproduce
eg: 1. open octane
2. import XXX.obj
3. add a material node and link to obj
4. click obj to start render
5. result should be a crash to desktop with crash report

-6- Any temp workaround you may have found
eg : I found that if I didnt apply the material before clicking the obj, it didnt crash

-7- Attachment of the offending .ocs or obj file that can help in the crash debug

Like I said, it's just a suggestion, but it's how I submit to other betas, and it gives a far more concise report for the devs instead of

"my octane crashes can you fix thanks."

cheers

cp

[DayVids]

tried this once already - see here

[cpember]

haha i KNEW something like it was posted here somewhere, but I couldnt find the damn post ( I was going to append it actually, but i couldnt remember what the thread topic was)


cheers

cp


ps: i mean, really, all that has to be done is copy/paste and fill it in

[Zay]

tried this once already - see here

Hehe, that's the problem when using a forum where you don't have a fast and clear overview. It would be nice if the dev team would set up a real bug report script like the PHPBB team has with their software. That's a great one!

[radiance]

Hi guys,

We do have an internal system, but not a public one yet.
We are looking into the matter, as the community is indeed growing too fast for a forum to provide propper bug reporting.

Yours,
Radiance