KUKSA.val Component Maturity

This is a suggestion on how to classify KUKSA.val components. Idea is to use PyPI classification as basis (Planning, Pre-Alpha, Alpha, Beta, Production/Stable, Mature, Inactive)

https://pypi.org/classifiers/ https://martin-thoma.com/software-development-stages/

Status	KUKSA.val Meaning	Components
Planning	No software exists	None
Pre-Alpha	In development	None
Alpha	Usable for Internal use, Demo and Proof-of-Concept	KUKSA.val SOME/IP Feeder, KUKSA.val Replay, KUKSA.val CSV Provider, KUKSA.val Example HVAC Service, KUKSA.val Example Seat Service, KUKSA.val Mock Service
Beta	Usable for Evaluation and Testing Purposes, well maintained	KUKSA.val DDS Provider
Production/Stable	Feature Complete, reasonably well tested, well maintained	KUKSA.val Client, KUKSA.val Databroker, KUKSA.val DBC Feeder
Mature	No new features planned, minimal maintenance	KUKSA.val Server, KUKSA.val Go Client, KUKSA.val GPS Feeder,
Inactive	No maintenance, not tested/updated when other components are updated
TBD	Components where no decision yet has been taken	S3 Uploader, Node red dashboard

Proposed Version Handling:

• If we release a new version of the server solutions (KUKSA.val Server and KUKSA.val Databroker) or the SDKs (KUKSA.val Python Client, KUKSA.val Go Client) we shall strive to test the "Production/Stable" and "Mature" components using or depending the updated server/SDK with the new server/SDK as soon as possible.

Any Production/Stable/Mature component shall always "work" with latest release server/SDK