ImranR98/apps.obtainium.imranr.dev
Proposal: Add a POLICY document for file structure and version conventions
Offen
#1.568 geöffnet am 30.07.2026
enhancementhelp wanted
Repository-Metriken
- Stars
- (553 Sterne)
- PR-Merge-Metriken
- (Keine gemergten PRs in 30 T)
Beschreibung
I propose that we add a POLICY document to structure how files should look and standardize conventions for version numbers.
Example Proposal: Standardize Unofficial Version Numbers
Some apps use unofficial version numbers when stable release formats cannot be applied. For example, the Nightly releases of RetroArch currently use a plain date format (YYYY-MM-DD) because the official version number cannot be added to them (e.g, 1.22.2):
The versionExtractionRegEx\":\"\\\\d{4}-\\\\d{2}-\\\\d{2}\" in these configuration files handles this format:
RetroArch: public/data/apps/complex/com.retroarch.jsonRetroArch (AArch64): public/data/apps/complex/com.retroarch.aarch64.jsonRetroArch (32-bit): public/data/apps/complex/com.retroarch.ra32.json
Proposed Rule
Unofficial version numbers should be enclosed in square brackets. Under this policy, plain dates like YYYY-MM-DD would be formatted as [YYYY-MM-DD] (e.g., for RetroArch Nightly builds).