Try a standardised versioning scheme using KDE Apps version
Diff Detail
- Repository
- R385 Bovo
- Branch
- version
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 11680 Build 11698: arc lint + arc unit
This should really be up to the maintainer, if there is one. If not, I think we should default to using the bundle version. Bovo's maintainer is listed as Pelladi Gabor <pelladigabor@gmail.com>, but I don't see a Phab account for Pelladi or any recent activity so I think it's safe to say that it's unmaintained. In such a circumstance, I think it's appropriate to use the bundle's own version to simplify the release process.
-1 this is a bad way to this stuff.
Why are you reinventing the wheel when we already have this solved?
Note this is just an example to try to get the right style. It also needs checking with maintainers or relevant teams that it's wanted.
But this does not change the *release* process.
This patch does in that this would then get increased by the increase_repos_version.sh script and added to bugzilla by the add-bugzilla-versions/add-versions.py and when someone gets round to it by a script that runs appstream-metainfo-release-update
IMNSHO the golden rule for this kind of patch is:
- is application part of KDE Applications? ☑
- has application has "relatively significant" code changes since the last time the version was updated? ☑ (gui/version.h was updated in 2015, there's been fixes since then)
So let's go with this.
You don't need a config-bovo.h file, instead use ECMSetupVersion to generate the version.h file.
right, see https://cgit.kde.org/ktuberling.git/commit/?id=10d753fce6718a147f0095d2274515bf96078292 for inspiration