Skip to content

Milestones

List view

  • Continuation of Refactor Build System (#97). #97 covers the original charter — dependency version upgrades, Qt6 migration, and Windows CI/packaging — and is largely complete. This milestone carries the build-system work identified after that charter was written, mostly filed 2026-08-05. Goals: - Give externals a real install stage so there is something cacheable and relocatable (#2627 and its children #2631-#2640) - Cut CI build time: sccache actually reaching the inner build (#2626, #2648), Superbuild external caching (#2520, #2628), Boost build and clone cost (#2548) - Modernize CMake: generator expressions, GenerateExportHeader, GET_RUNTIME_DEPENDENCIES, debug postfix, consistent output dirs (#2200, #2203, #2649, #2651, #2652, #2653, #2654, #2655, #2656) - Dependency update flow and version manifest (#2480, #2550) - Packaging and deployment: Windows installer to WiX/MSI (#2650), macOS @rpath and bundle fixes (#1269), build.sh modernization (#2235), offline and archive builds (#191, #902), Docker (#1720), Linux install location (#1396) - Platform build verification: macOS deployment target (#2565), Ubuntu Qt6 and runtime checks (#2563, #2556) - CI infrastructure: branch-protection rulesets (#2518), coverage reporting (#1137), workflow improvements (#2028, #2487, #2562) Sequencing note: the externals-install program (#2627, #2631-#2640) is deliberately deferred until the VTK renderer branch `refactor_add_vtk` merges. #2637 repoints ~37 SCI_* export sites across Superbuild/, which is the same surface VTK 9.6.1 is being added to, so the two cannot land concurrently. That chain is also strictly serial (verify harness -> audit -> convert -> repoint -> platform fixups -> measure). Everything outside that program is startable now.

    Due by December 30, 2026
    0/50 issues closed
  • Post-5.0.0 feature work.

    No due date
    0/31 issues closed
  • Build system for a SCIRunPy package and distribution on PyPi.

    Due by July 31, 2027
  • Use python wrappers to implement pytest suite. The priority of this suite is UI and other api features, to complement the google test suite.

    Due by March 31, 2027
  • Use the python wrapper factory to generate wrappers for the full SCIRun library

    Due by March 31, 2027
  • Utilize VTK to automate python wrapping of SCIRun functions

    Due by January 31, 2027
  • refactor the Python interface with SCIRun to facilitate: - python wrapping - external python library support - native python scripting - better IWP module - standalone python modules Good examples of many of the features we are looking for are Slicer and Blender

    Due by October 31, 2026
    0/8 issues closed
  • After user study and significant testing of the vtk rendering system, transition the main renderer to VTK instead of SR

    Due by October 31, 2026
    0/1 issues closed
  • design and execute a user survey to solicit feedback for newly developed renderer and interface

    Overdue by 1 month(s)
    Due by July 31, 2026
  • testing the VTK renderer with multiple use cases.

    Due by January 31, 2027
  • Implement a VTK renderer to run in parallel to or instead of the native SR version There is an incomplete example of how to do this in Seg3D with the following fork/branches: https://github.com/sankhesh/Seg3D/tree/vtk_rendering https://github.com/sankhesh/Seg3D/tree/vtk_rendering_new

    Overdue by 1 day(s)
    Due by August 31, 2026
    0/6 issues closed
  • The SCIRun build system needs to be refactored to accommodate new dependencies and toolchains. The goals of this milestone are: - Modernize the CMake Superbuild and dependency-update flow (#2480, #2550) - Update external dependency versions (Boost, Qwt 6.3, Tetgen 1.6, Freetype, zlib, Python) - Qt 6 compatibility and migration, incl. Windows-specific fixes (#2221) - Windows CI, build & packaging: GitHub Actions, CPack installer, Win 11/2022 runners - CI/infrastructure: branch-protection rulesets, test-results tracking Scope that was originally listed here has been split into its own milestones: - VTK for renderer → VTK renderer (#98) - Multiple-renderer / headless rendering → Refactor Visualization Layer (#96) - More complete python wrapping, redesigned python layer, additional python libraries (numpy/scipy) → Refactor Python interface (#102) Some Seg3D branches that may help with the VTK work (now tracked in #98): https://github.com/SCIInstitute/Seg3D/pull/407 https://github.com/sankhesh/Seg3D/tree/vtk_rendering https://github.com/sankhesh/Seg3D/tree/vtk_rendering_new

    Overdue by 8 day(s)
    Due by August 24, 2026
    68/97 issues closed
  • Separate the renderer from the data management and UI layers with the following goals: - allow for multiple renderer options (VTK) - further scripting features - headless options (aspirational) There is an example of this process in Seg3D with the following fork/branches: https://github.com/sankhesh/Seg3D/tree/vtk_rendering https://github.com/sankhesh/Seg3D/tree/vtk_rendering_new

    Due by September 30, 2026
    0/3 issues closed
  • No due date
    0/201 issues closed
  • No due date
    55/172 issues closed
  • For new developers and contributors to learn the system.

    No due date
    0/33 issues closed
  • For all unscheduled, yet essential, features.

    No due date
    1/57 issues closed