In data giovedì 4 ottobre 2018 00:34:04 CEST, Sandro Knauß ha scritto: > KMyMoney 4.8.1.1 was thrown out of testing for a long time now.
September 15th, which makes it not even a month... > KMyMoney > 5.0.1 was uploaded to experimental for half a year. Me personally used > KMyMoney 5.0.1 without any issue. Are there any blockers against uploading it > to unstable? TL;DR: just don't. 1) various upstream bug reports with regressions in 5.0 compared to 4.8 2) commits with fixes like "restore behaviour broken in the porting to Qt5/Frameworks" 3) a poor handling of upstream of the "stable" branch: after 5.0.1 (released a couple of weeks after 5.0.0), it was almost completely ignored... until the last month, when upstream released a new stable release was needed, and they merged master to 5.0 (yes, including new features, heavy refactoring, etc) 4) a very poor handling of releases: releases announced but delayed, releases announced only for Windows, in general no mindset about "release early, release often", and so on 5) the fact that kmymoney is a financial application that deals also with real money (doing bank transations and so on) This makes it very hard to properly follow what upstream does, and make sure that it causes no regressions (compared to 4.8.x). Just a recent example of this: they originally planned to release kmymoney 5.0.2 ~10 days ago or so [1]; to do that, as I wrote above, they merged the development git master to the stable 5.0 branch; the expected result is "broken DB", and release postponed [2]. [1] https://mail.kde.org/pipermail/kmymoney-devel/2018-September/021485.html [2] https://mail.kde.org/pipermail/kmymoney-devel/2018-September/021768.html The current state of kmymoney 5.x is just sad. -- Pino Toscano
signature.asc
Description: This is a digitally signed message part.
-- https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-talk
