[Bf-committers] Bug reports: requiring "Worked in" field

Howard Trickey howard.trickey at gmail.com
Thu Mar 12 12:16:46 CET 2020

How far back in versions do you expect people to check?
I imagine sometimes, even often, the answer is "never". E.g., some new code
has been added and a user has run into a case where that new code crashes.

Maybe an exception should be made for crashes?

On Thu, Mar 12, 2020 at 6:43 AM Sybren A. Stüvel via Bf-committers <
bf-committers at blender.org> wrote:

> Hello list,
> When investigating a bug report, it can be very helpful to know when an
> issue was introduced. I had a little discussion with Dalai on
> #blender-coders, and we decided to make a change in the bug reporting
> template [1]. The "Worked" field, where people fill out what version of
> Blender still worked properly for them, is now no longer optional.
> [1] https://developer.blender.org/maniphest/task/edit/form/1/
> Of course we take a human approach to this, and there will be valid
> reasons why this version cannot be determined or is otherwise
> irrelevant. For the majority of bugs, however, it can be very helpful if
> the reporter checks with older versions of Blender.
> I want to suggest the following before accepting/confirming a report:
>   * We should ask the reporter to test with older versions of Blender
>     (if not done already), and
>   * The example blend file should be openable with that version.
> The latter point is to prevent cases like "this worked in 2.79, here is
> a 2.83 file to reproduce the issue".
> I'm confident that the ability to quickly see the correct behaviour and
> the problematic behaviour will help in the speed at which we can resolve
> issues.
> Cheers,
> Sybren
> --
> dr. Sybren A. Stüvel
> Blender Software Developer
> https://blender.org/
> https://cloud.blender.org/
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list