List view

• Maintenance

  Candidate tasks for the annual maintenance of the application.

  Due by September 30, 2026

  •0/8 issues closed
  0% complete8 open0 closed

• Ongoing support (for urgent issues)

  More urgent bug fixes as they are discovered. Anything that blocks or severely impedes the annotation workflow. This group of tasks should take precedence over any others (e.g. Features or Change Freeze). They can be added anytime. But their completion will reduce the time we can spend on Features or Change Freeze.

  Overdue by 1 month(s)

  •

  Due by September 30, 2025

  •3/3 issues closed
  100% complete0 open3 closed

• Last features

  Outstanding or new features to be considered before we move into Change Freeze.

  Overdue by 1 month(s)

  •

  Due by September 12, 2025

  •9/9 issues closed
  100% complete0 open9 closed

• Change Freeze

  Primary purpose is the robustness and sustainability of the resource and data beyond September 2025. Examples: non-blocking bugs, refactoring to consolidate the code, testing, documentation, clean up data and code base, upgrade the software stack. Change Freeze marks the definitive end of the work on new or outstanding features (because they often introduce new bugs, which is counter to what Change Freeze stands for).

  Overdue by 1 month(s)

  •

  Due by September 30, 2025

  •17/17 issues closed
  100% complete0 open17 closed

• Backlog

  Un-categorised tickets open before June 2025. We may move some of those into the Change Freeze and prioritise them.

  Overdue by 1 month(s)

  •

  Due by September 30, 2025

  •80/87 issues closed
  91% complete7 open80 closed