[Bf-committers] Proposal for handling bug reports
blueprintrandom1 at gmail.com
Tue Jul 1 21:17:30 CEST 2014
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 community is pretty quick to point out stuff they have felt with.
On Jul 1, 2014 12:07 PM, "Sergey Sharybin" <sergey.vfx at gmail.com> wrote:
> I totally support the proposal. We can start doing it right away :)
> On Wed, Jul 2, 2014 at 12:36 AM, Campbell Barton <ideasman42 at gmail.com>
> > 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 to issues, ask user to follow our guidelines
> > and submit blend files,
> > asking what version of Blender they use etc...
> > Its demotivating to have 100's of reports and try tackle the bug tracker,
> > only to find many reports which are in some unknown status where
> > nobody can redo the problem or understands what it is.
> > Even being more strict and moving issues to TODO, only helps so much.
> > So I'd like to do this a bit different:
> > Proposal
> > ========
> > * add "Blender: Unconfirmed" project.
> > * If we get a valid bug report but can't redo it, we move immediately
> > to "Blender: Unconfirmed" with a canned response.
> > * 2 other people need to check the report.
> > * If after 2 weeks nobody can redo the issue, we close it.
> > This means users have some more responsibility to have others check
> > bugs, and redo.
> > It does risks closing valid issues sometimes, but at this point we
> > just have a bugs nobody can redo and nobody replies
> > to, so they arent useful to have open.
> > If the bug really happens for others probably it gets reported again
> > anyway.
> > Of course if a report is incomplete we still mark as incomplete, if
> > its a TODO, move it,
> > this is for valid reports which give steps we can follow, but no way
> > to redo the bug.
> > Examples
> > ======
> > - https://developer.blender.org/T40881
> > - https://developer.blender.org/T40877
> > - https://developer.blender.org/T40870
> > - https://developer.blender.org/T40864
> > - https://developer.blender.org/T40858
> > - https://developer.blender.org/T40838
> > - https://developer.blender.org/T40788
> > - https://developer.blender.org/T40787
> > - https://developer.blender.org/T40784
> > - https://developer.blender.org/T40753
> > - https://developer.blender.org/T39591
> > - https://developer.blender.org/T34962
> > - https://developer.blender.org/T39467
> > --
> > - Campbell
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> With best regards, Sergey Sharybin
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers