On 01.07.2014 20:36, Campbell Barton wrote:
If the bug really happens for others probably it gets reported again anyway.
Thats risky -- make sure to be clear about why the bug report was
closed. It’s disappointing and demotivating if, as a user, you find a
bug report for your specific problem
Any suggestion for hardware specific reports?
In the game engine tracker, I am adding platform specific bugs that I can
not test to 'Platform: Windows' etc, but I am unsure about what to do with
reports based on features my GPU does not support or input devices that I
(or any other active dev)
I'm against about automation. Not only because trying to lang it to the
phab code would add extra PITA maintaining the server, but also because it
shouldn't really use some strict rules and use common sense instead.
As for confirmed status -- i dunno. Don't really think it's so much a
hassle to
Is it possible to run blender In debug mode, so when a crash happens I know
what it was doing when it crashes? I could learn a lot that way, and you
could crl+printscreen the error
On Jul 1, 2014 11:30 PM, Sergey Sharybin sergey@gmail.com wrote:
I'm against about automation. Not only because
It could only work reliably for the official builds, for which we can have
debug symbols. Otherwise users will need to use blender with debug symbols
all the time and this bumps blender size by around an order of magnitude.
It's also quite often not enough to know backtrace, it's also needed to
Would it be possible to make the existing report a bug operator in
/info help /automatically fill in the hash and system info?
Maybe an item in file menu like Save for Bug Report could generate system
info and save it in requested .blend file.
System info would probably be attached more
Recently we've been getting more bug reports, and its getting to a
point where I don't think we can usefully manage them.
Or, to do so, takes more and more time away from development.
A lot of the work ends up being communication and many times they
aren't even real bugs.
Just the time to reply
I totally support the proposal. We can start doing it right away :)
On Wed, Jul 2, 2014 at 12:36 AM, Campbell Barton ideasma...@gmail.com
wrote:
Recently we've been getting more bug reports, and its getting to a
point where I don't think we can usefully manage them.
Or, to do so, takes more
I had a few bugs in the tracker, that were actual bugs, but took a
exceedingly long time to sort out and then work around, then not fix
because the work around was sufficient. One nice thing would be a place at
BA where a bug could get looked at and confirmed as a bug, then submitted,
the
I totally support the proposal. We can start doing it right away :)
(yes, I’m plagiarizing some famous russian guy here, I know…)
Le 01/07/2014 21:07, Sergey Sharybin a écrit :
I totally support the proposal. We can start doing it right away :)
On Wed, Jul 2, 2014 at 12:36 AM, Campbell
It seems to me there could be an active open call for volunteers on this
matter: you can help Blender with no technical background, help us
confirm and substaciate bugs. I think (hope) there are many people out
there, willing to do something to help, and feeling sorry they lack the
skills. This
I support this. :)
Can we automate the process a bit though? Like, if 2 other users can confirm
the issue, the report becomes „Confirmed“ and part of the regular BF-Blender
project again, or auto close it, if no one can confirm it in 2 weeks. Otherwise
we also have to regularly check the
@Jacob Merrill, What your suggesting sounds more like a
troubleshooting resource, Probably we should have this in our manual -
list common gotcha's, solutions. The issue with first reporting
issues on a forum is users have to report twice and have logins to
both systems, so wouldnt want to make
Ok, lets see how this goes: https://developer.blender.org/project/view/50/
On Wed, Jul 2, 2014 at 11:37 AM, Campbell Barton ideasma...@gmail.com wrote:
@Jacob Merrill, What your suggesting sounds more like a
troubleshooting resource, Probably we should have this in our manual -
list common
Many users forget to add even the basic system informations in the bug
reports or probably just don't know what to write there.
Perhaps the first few rows of the system-info.txt should be a copy-paste
part for bug reports, or let's add a new 'bug report to clipboard'
function in the help menu
Would it be possible to make the existing report a bug operator in
/info help /automatically fill in the hash and system info?
On 07/01/14 22:19, Fazekas László wrote:
Many users forget to add even the basic system informations in the bug
reports or probably just don't know what to write
16 matches
Mail list logo
