Bug #535 has existed for a little bit and appears to have fallen through the cracks. I encountered it later in the development environment and I believe I have fixed it (todo: confirm this) but that fix should have happened sooner.
The release process must be updated to include a phase for reviewing the open bugs.
label:bug OR no:label shows 29 open items.
While it may be impractical to say that "all bugs must be fixed for the next release to be allowed to be published" it may be more achievable to say "the number of bugs at the time of the newest release must be less than the number of bugs at the time of the previous release" which would converge over time to there being zero bugs as any releases must concede some bug fixes.
Perhaps a "fix the oldest bug" approach would also be beneficial to avoid stagnation.
Bug #535 has existed for a little bit and appears to have fallen through the cracks. I encountered it later in the development environment and I believe I have fixed it (todo: confirm this) but that fix should have happened sooner.
The release process must be updated to include a phase for reviewing the open bugs.
label:bug OR no:label shows 29 open items.
While it may be impractical to say that "all bugs must be fixed for the next release to be allowed to be published" it may be more achievable to say "the number of bugs at the time of the newest release must be less than the number of bugs at the time of the previous release" which would converge over time to there being zero bugs as any releases must concede some bug fixes.
Perhaps a "fix the oldest bug" approach would also be beneficial to avoid stagnation.