Skip to content

ziviDomeLive 2.0.0 Release Readiness Procedure Template

Procedure template, not release status

Unchecked boxes below are a reusable execution protocol and never represent the status of a particular candidate. The authoritative result is maintainer/release-evidence.md together with the CI qualification artifact bound to its declared source SHA. Any later source change makes that evidence stale until the entire applicable procedure is repeated.

The tag is not a test

Create v2.0.0 only after every applicable gate below has recorded evidence. A source-level capability is not qualification evidence.

This is the final gate before creating v2.0.0. A checked item means evidence exists; it does not mean the feature merely exists in source.

1. Automated

  • clean/test/build passes
  • qualificationTests passes
  • documentation validation passes
  • MkDocs strict EN/PT passes
  • buildReleaseArtifacts passes
  • final package structure validated

2. GPU visual

  • Standard
  • Domemaster
  • Equirectangular
  • Skybox
  • CalibrationTool
  • Environment visual-background contract
  • representative resolution switch / resetGraphics(int)

Transparent-background physical matrix

Use a Scene that draws neither background(...) nor fullscreen geometry. Inspect alpha, not only the displayed RGB result; a black checkerless receiver is not sufficient evidence of opacity or transparency.

View Environment absent Environment disabled Environment enabled Main preview Final/output target
Standard [ ] [ ] [ ] [ ] [ ]
Domemaster [ ] [ ] [ ] [ ] [ ]
Equirectangular [ ] [ ] [ ] [ ] [ ]
Skybox [ ] [ ] [ ] [ ] [ ]

For Domemaster, repeat with Size%=100, Size%=50 and Size%=0. Verify alpha zero outside the circle at 100/50, transparent newly exposed area at 50, and a fully transparent target at zero. Then inspect every applicable receiver separately: NDI on each claimed platform, Syphon on macOS and Spout on Windows. Record when a receiver discards alpha as a receiver limitation; do not turn that limitation into an opaque internal framebuffer fallback.

3. Benchmark

  • BenchmarkTool smoke
  • CPU baseline
  • CPU/GPU measurement mode supported by the current tool
  • benchmark report archived with exact environment

4. Native output

  • NDI receiver evidence for each platform claimed
  • Syphon receiver evidence for macOS if macOS is claimed
  • Spout receiver evidence for Windows if Windows is claimed

Do not infer Linux/macOS/Windows qualification from source compatibility alone.

5. Installed Processing package

  • install generated ZIP/PDEX in a clean Processing sketchbook
  • Javadocs open from reference/index.html
  • source included as intended
  • eight learning examples open/run
  • CalibrationTool opens/runs
  • BenchmarkTool opens/runs
  • no test sources or generated benchmark reports in the package

6. Publication metadata

  • library.properties validated
  • stable ZIP/TXT/PDEX generated together
  • README/MkDocs/CFF/Zenodo version and DOI consistent
  • tested-platform claims equal recorded evidence
  • documentation DOI/ISBN remain absent/null until real registration

7. Freeze

  • CHANGELOG reflects the implementation actually shipped
  • no current guide describes roadmap work as implemented
  • no deprecated 1.x terminology contaminates 2.0 tutorials except explicit migration/history notes
  • no generic VR/headset/stereo runtime claim remains without an implementation contract
  • no renderer/API change was introduced solely to make documentation easier

Only after all applicable evidence is complete should the maintainer create v2.0.0.