tumblesle-release compares with reference that might be pruned from openQA already

[okurz]

observation

[Notice] -hermes to #qa-review- [07:05:30] tumbleSLE release: build: 0405
<c> [07:09:37] that is good?
<c> [07:11:28] that was a forced release? because 405 is not even tested
<okurz> tumblesle_release:0405: 1/0 vs. 0234: 1/1, clearly 1 passed+0 failed
is better than 1 passed and 1 failed ;-) but why does have the last tumblesle
release 1/1?

problem

https://oqXXX/group_overview/XX?limit_builds=200 shows the problem. 0234 is the reference but only 2 jobs still exist from that old "non-important" job so tumblesle-release should probably tag the last release

further details

I guess you can see it as a feature: if no build gets released for a very long time it just picks the most recent one