[Bf-committers] What about adding a bcon-debug phase?

Campbell Barton ideasman42 at gmail.com
Mon Mar 9 12:43:37 CET 2015

On Mon, Mar 9, 2015 at 7:24 PM, Gaia <gaia.clary at machinimatrix.org> wrote:
> Would it be an idea to add a bcon-debug phase, which is dedicated to
> fixing Bugs which are complicated to fix or take long time to fix?
> bcon-debug would start right AFTER release and could last until a specific
> predefined goal is reached like:
> - certain amount of bugs has been fixed,
> - a specified set of bugs has been fixed,
> - the 2 oldest bugs in the tracker are fixed
> - bug count has fallen below a threshold
> - ... whatever makes sense here.
> Also bcon-debug would be a time where only old reported bugs which
> had been reported BEFORE release can be fixed.
> If the end of bcon-debug is defined by reaching the goals rather than
> reaching
> a point in time, then this might be a good motivation for developers to help
> getting the bad bugs out of the system as soon as possible, because only
> then
> they can proceed with new shiny stuff ;-)

Hi Gaia,

Would rather do bugfixing for larger, riskier areas along with other
regular development, (bcon1-2)
If we have this as apart of the release-cycle it wont make sense for
many areas of Blender.

> cheers,
> Gaia
> On 09.03.2015 07:54, Campbell Barton wrote:
>> As long as we fix regressions, I don't think another week for fixing
>> is needed, its even risky when we have to make big changes for long
>> standing bugs right before release [1]
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

- Campbell

More information about the Bf-committers mailing list