On 11/9/19 1:36 AM, Dominique Leuenberger / DimStar wrote:
On Fri, 2019-11-08 at 15:57 +0100, Manfred Hollstein wrote:
sorry guys, is this a Kindergarden? Can't we all hold breath for 10 seconds, then think about it, and _then_ write a response? This is really far from attracting people to jump onto an openSUSE wagon...
Sure, you're right.. I'm sorry for letting me drag into this.
To sum it up: I switched the macro to %_binarychangelogtrim 0,1514764800,10 which makes use of the Macro pointed out by Michael.
So, we keep now at least the 10 most recent changelog entries (if there are so few, there is likely no big win, size-wise, to drop them too) and if there are more entries, we cut at Jan 1 2018 (2 years worth of changelog on a rolling distro should be sufficient; imho even this is a lot)
Rather then making it an fixed two years and given that Tumbleweed is not just a rolling release but the base for several stable distro's as well. maybe we should set the date so that its which ever is longer out of 2 years and when we branched the last SLE / Leap out of tumbleweed, so that when we got to branch SLE / Leap 16 all the changes files still contain all entries since Leap 15 was branched so its easy to see a clear list of changes. Then once 16 is branched we can periodically update the date to trim 2 years worth of entries until we get to 2 years after 16 was branched, then we wait until 17 to trim again. etc Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B