OS versions vs app versions vs backend changes
A practical rule for deciding what type of release a School-GIT change requires.
referencestatus
Release managers · Developersaudience
School-GIT docssource
SCHX nativeruntime
SCHX / FEATURE LAYER
Source map
- components/cdn/*
- lib/cdn/apps/*
- lib/cdn/os/*
- server.js
SCHX / FEATURE LAYER
OS update
Use an OS release when shared client shell behavior changes.
- Desktop
- WindowManager
- CustomCursor
- Taskbar / Start
- System Settings
- built-in OS applications
- shared browser OS services
SCHX / FEATURE LAYER
Web Bro app update
Use an app version when one installable app package changes. Existing immutable versions remain unchanged and a new semantic version is published.
SCHX / FEATURE LAYER
Backend-only change
A server.js optimization or internal API implementation fix does not automatically require an OS release if the browser contract stays compatible. If the API contract changes and the OS must change with it, publish compatible server and OS updates deliberately.
SCHX / FEATURE LAYER
Version number guidance
Patch versions fit bug fixes, minor versions fit backward-compatible features, and major versions fit breaking runtime or compatibility changes.
SCHX / FEATURE LAYER