Dev process improvement (new statuses, etc.)

Created on 21 March 2012, over 13 years ago
Updated 29 August 2025, 24 days ago

We can probably improve core development process with some simple improvements:

  • Add a "blocked" status for deadlocked issues
  • Explicitly timebox key issues; A leader would be able to extend the timebox if the conversation was not "done"
  • Develop an assignment process to trusted leaders when the issue has not been able to go forward.
  • Determine committability of an issue/design long before the actual RTBC or commit (and mark it as such). This makes the bikeshed happen (if necessary) well before the final commit point.

Other simple thoughts for core process improvements?

✨ Feature request
Status

Closed: outdated

Component

Policies

Created by

πŸ‡ΊπŸ‡ΈUnited States rfay Palisade, CO, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡ΏNew Zealand quietone

    It has been 13 years since this was discussed. That suggests people have managed with the existing statuses, whether we all like them or not.

    Related to this is an issue collecting all the issues about issue management, 🌱 [meta] Improve issue management Active . There is also the Bug Smash Initiative that has done much to triage and close duplicates and outdated issues. And the Needs Review Initiative is also keeping the number of issues at needs review in a more manageable state. And the total number of issues is being reduce by the identifying stale and very old issues and requesting confirmation that they are still a problem.

    There is also work being done to add active subsystem and topic maintainers and remove inactive ones.

    All these steps help to improve the issue throughput with, to me, is the goal.

    Therefore, closing this as outdated.

Production build 0.71.5 2024