Skip to content

Milestones

List view

  • 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.

    Due by September 30, 2025
    0/1 issues closed
  • Outstanding or new features to be considered before we move into Change Freeze.

    Overdue by 5 day(s)
    Due by July 31, 2025
    2/9 issues closed
  • 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).

    Due by September 30, 2025
    2/26 issues closed
  • Un-categorised tickets open before June 2025. We may move some of those into the Change Freeze and prioritise them.

    Due by September 30, 2025
    78/82 issues closed