Version:           unspecified (using Devel) 
OS:                Linux

KDE hosts not only its own code at its git and svn repositories but quite a few related ones. However, as long as KDE software gets branched periodically according to its releases, those extra projects don't and it'd really be nonsense to demand them to keep up with KDE releases once they're not KDE's per se.

But I've seen a good amount of times people asking for them to change version number to relate to KDE's (I've seen it this week at kde-apps.org). While, as said, it's not applicable, it shows that user would make use of a relationship between projects.

Also, for people who build and update their KDE and those extras from source but don't want or can't afford to get possible trouble with master (a break here and there 'cause of a code change), this sort of relationship would be quite a painkiller, as they not only wouldn't need to be looking for each project's stable branch to adjust their scripts as they'd also no longer have no need to keep pace with each project's release in order to get them updated.

That being, I'd like to suggest a sort of a rule (specially if this can be automated, to which I'm a layman) or agreement for all KDE hosted projects to have a "stable" (or alike) branch or tag (again, I don't know which'd be the best option, specially for automating it) that always leads to their latest stable release, so that if user wants to checkout bleeding edge stable KDE and related extras (at first time or to keep them updated) s/he only needs to use "stable" branch or tag for each one, no matter which their version number is.

Reproducible: Didn't try



Expected Results:  
User could get and keep their softwares at their latest stable release of any project hosted inside KDE git/svn structure by just checking out "stable" (or alike) branch, no matter which are their version numbers.