-
Notifications
You must be signed in to change notification settings - Fork 51
KUKSA.val Component Maturity
Erik Jaegervall edited this page Jul 18, 2023
·
6 revisions
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.
- If no-one volunteer to test/update the "Production/Stable" and "Mature" components then they may be degraded to "Inactive"
Any Production/Stable/Mature component shall always "work" with latest release server/SDK
Proposed maintenance strategy:
- If a bug or vulnerability is found - fixing it should have a high priority if the component is in state Beta, Production/Stable or Mature
- Exception: Individual features in "Production/Stable" components may be considered as "Mature" or "Inactive"
- For Pre-Alpha/Alpha fixing bugs and vulnerabilities has no priority, focus is in on feature growth
- If no-one volunteer to fix "Production/Stable" and "Mature" components then they may be degraded to "Inactive"