[Bf-committers] Tracker curfew to start on Monday
Nathan 'jesterKing' Letwory
nathan at blender.org
Mon Dec 23 14:57:59 CET 2019
This is a good question. How to ensure these todos and know
issues stay updated. Essentially this is part of what module
owners should manage: for each release cycle go over the
known issues and todos for their module. Update descriptions
where necessary, thus ensuring they stay relevant.
When module owners start planning work they should take
these into account as well. When an old issue (known issue
or todo) is moved to be handled for a release cycle it then
can be set to be bug again.
That should cover screening and revisiting old issues, at
the same time ensuring they stay up-to-date.
On Sat, 21 Dec 2019 at 03:47, Aaron Carlisle <carlisle.b3d at gmail.com> wrote:
> One question that I have is how will known bugs and issues be documented
> In the past, there has been a list of todos on the old wiki which often
> became quickly out of date.
> These have since been copied and pasted to
> https://developer.blender.org/project/board/53/ (in the wiki column)
> these tasks are just collecting dust there also.
> What needs to happen is a way that these issues can be documented well and
> stay up to date.
> In the process of these old todos need to be screened and integrated into
> this new method of logging reports.
> Aaron Carlisle
> On Fri, Dec 20, 2019 at 11:15 AM Dalai Felinto <dfelinto at gmail.com> wrote:
> > Hi,
> > On Monday, Blender begins a tracker curfew.
> > Please check the teaser video: https://www.youtube.com/watch?v=HDE2ARiN1a0
> > A more complete document will follow suit, but the gist is: from now on the
> > Blender Foundation is going to adhere to a strict definition of what a bug
> > is.
> > * It is only a bug if the code was intended to work and it fails, or when a
> > an issue used to work and it fails.
> > * It is only a bug if the module is in active maintenance. Otherwise it
> > might be registered as known issue.
> > * If a bug fix takes more than a day, it is not a bug, it is a development
> > task (if parts of the module plans) or a feature request (which we don’t
> > support at the moment).
> > * If a bug won’t be worked on for the upcoming 6 months, it is not a bug,
> > it is a known issue that needs to be documented.
> > The developers under contract will dedicate 2 full-days a week to work in
> > the tracker to re-triage issues, fix bugs and patch review.
> > Some stats following this definition. From a universe of 2,042 open reports
> > Blender has:
> > * 631 untriaged reports.
> > * 37 confirmed high priority bugs.
> > * 1,367 reports that may be either a bug or a known issue
> > In the end the tracker curfew is to bring confirmed bugs down to a
> > manageable number (~200). There is a similar goal for patch review, but I
> > will leave this for the official code.blender.org post next week.
> > Have a great weekend,
> > Dalai
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> Aaron Carlisle
> Project administrator for the Blender 3D Documentation Project
> Email: carlisle.b3d at gmail.com
> Website: https://blendify.github.io
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers